Social Processing Member Offering Fixed and Intelligent Services

ABSTRACT

A social networking system offers a variety of fixed and intelligent services and social device resources participating as members in a social network (SNET) group. Such members may include, for example, social billing and payment services, digital assistants and artificial intelligence functions, robotic control and training services, media content storage and playback services, data backup services, services that support distributed processes such as distributed research projects, networking elements such as network attached storage (NAS), firewalls, proxies, etc. In various embodiments, such services and resources may become available upon being selectively docked or otherwise associated (e.g., through docking of a supporting device) with a SNET group by a human member or third party via a docked user device. Selection of available services may be supported through a visual menu provided by a member device or support service.

CROSS REFERENCES TO PRIORITY PATENTS/PATENT APPLICATIONS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. §120 as a continuation of U.S. Utility patent application Ser.No. 13/484,624, entitled “SOCIAL PROCESSING MEMBER OFFERING FIXED ANDINTELLIGENT SERVICES,” filed May 31, 2012, co-pending, and to be issuedas U.S. Pat. No. 9,055,121, which:

1. claims priority pursuant to 35 U.S.C. §119(e) to U.S. ProvisionalPatent Application Ser. No. 61/545,147, entitled “SOCIAL NETWORK DEVICEMEMBERSHIPS AND RESOURCE ALLOCATION,” filed Oct. 8, 2011, expired; and

2. claims priority pursuant to 35 U.S.C. §120, as a continuation-in-part(CIP), to the following U.S. Utility patent applications:

-   -   a. U.S. Utility patent application Ser. No. 13/342,301, entitled        “SOCIAL NETWORK DEVICE MEMBERSHIPS AND APPLICATIONS,” filed Jan.        3, 2012, to be issued as U.S. Pat. No. 9,065,869;    -   b. U.S. Utility patent application Ser. No. 13/408,986, entitled        “SOCIAL DEVICE RESOURCE MANAGEMENT,” filed Feb. 29, 2012,        co-pending; and    -   c. U.S. Utility patent application Ser. No. 13/436,557, entitled        “SOCIAL NETWORKING GROUPING HIERARCHY” filed Mar. 30, 2012, to        be issued as U.S. Pat. No. 9,060,036, which claims priority        pursuant to 35 U.S.C. §120, as a continuation-in-part (CIP) to        U.S. Utility patent application Ser. No. 13/351,822, entitled        “AD HOC SOCIAL NETWORKING,” filed Jan. 17, 2012, co-pending;        all of which are incorporated herein by reference in their        entirety.

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

The invention relates generally to social networking; and, moreparticularly, it relates to social network device memberships, resourceallocation, and service offerings.

2. Description of Related Art

The popularity and growth of social network sites and services hasincreased dramatically over the last few years. Present social networksites include Facebook®, Google+®, Twitter®, MySpace®, YouTube®,LinkedIn®, Flicker®, MYUBO™ Bebo® and the like. Such social networking(SNET) sites are typically web-based and organized around user profilesand/or collections of content accessible by members of the network.Membership in such social networks is comprised of individuals, orgroupings of individuals, who are generally represented by profile pagesand permitted to interact as determined by the social networkingservice.

In many popular social networks, especially profile-focused socialnetworks, activity centers on web pages or social spaces that enablemembers to view profiles, communicate and share activities, interests,opinions, status updates, audio/video content, etc., across networks ofcontacts. Social networking services might also allow members to trackcertain activities of other members of the social network, collaborate,locate and connect with existing friends, former acquaintances andcolleagues, and establish new connections with other members.

Individual members typically connect to social networking servicesthrough existing web-based platforms via a computing device, tablet orsmartphone. Members often share a common bond, social status, orgeographic or cultural connection with their respective contacts.Smartphone and games-based mobile social networking services areexamples of rapidly developing areas.

In so-called “cloud” computing, computing tasks are performed on remotecomputers/servers which are typically accessed via Internet connections.One benefit of cloud computing is that may reduce the relativeprocessing and storage capabilities required by user devices (e.g., acloud computer may load a webpage accessed by a tablet device andcommunicate only required information back to the tablet). Accordingly,recent years have witnessed an ever-growing amount of content andapplication software being migrated from local or on-site storage tocloud-based data storage and management. Such softwarefunctionality/services and content are typically available on-demand via(virtualized) network infrastructures.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates a social network group comprising social services anddevices in accordance with an embodiment of the disclosure.

FIG. 2 illustrates a social group comprising a variety of members inaccordance with an embodiment of the disclosure.

FIG. 3 is a functional block diagram illustrating a social networkinfrastructure and social resources/devices in accordance with anembodiment of the disclosure.

FIG. 4 is a functional block diagram of various embodiments of a socialnetwork group offering fixed and intelligent services and networkelements in accordance with the disclosure.

FIG. 5 is a functional block diagram of an artificial intelligence(AI)/robotic social network group in accordance with an embodiment ofthe disclosure.

FIG. 6 is a schematic block diagram of an embodiment of a social set-topbox (STB)/gateway in accordance with the disclosure.

FIG. 7 is a schematic block diagram of a social device operable tosupport various interactions between other social devices and socialservices and systems in accordance with an embodiment of the disclosure.

FIG. 8 illustrates a schematic block diagram of a social networkinggrouping hierarchy according to various embodiments of the disclosure.

FIG. 9 illustrates a schematic block diagram of representative resourceviews according to various embodiments of the disclosure.

FIG. 10 illustrates a schematic block diagram of social networkinggroupings and representative resource views according to variousembodiments of the disclosure.

FIG. 11 illustrates a schematic block diagram of social networkinggrouping hierarchies according to various embodiments of the disclosure.

FIG. 12 is a schematic block diagram illustrating access to socialservices and other resources participating in a social networkgroup/sub-group in accordance with an embodiment of the presentdisclosure.

FIG. 13 is a logic diagram of a method for allocating social resourcesand services in accordance with an embodiment of the present disclosure.

FIG. 14 is a logic diagram of a method for establishing tiered views ofand access to social resources and services in accordance with anembodiment of the present disclosure.

FIG. 15 is a logic diagram of a method for arbitrated access to socialresources/robotics in accordance with an embodiment of the presentdisclosure.

FIG. 16 is a schematic block diagram illustrating remote access tosocial resources of a social network circle/sub-circle in accordancewith and embodiment of the present disclosure.

FIG. 17 is a schematic block diagram of an embodiment of a social devicecomprising integral functionality operable to support social networkcircle/sub-circle membership and communications in accordance with thedisclosure.

DETAILED DESCRIPTION OF THE INVENTION

As used herein, the terms “social network” and “SNET” comprise agrouping or social structure of devices and/or individuals, as well asconnections, links and interdependencies between such devices and/orindividuals. Members or actors (including devices) within or affiliatedwith a SNET may be referred to herein as “nodes”, “social devices”,“SNET members”, “SNET devices”, “user devices” and/or “modules”. Inaddition, the terms “SNET circle”, “SNET sub-circle”, “SNET group” and“SNET sub-group” generally denote a social network that comprises socialdevices and, as contextually appropriate, human SNET members andpersonal area networks (“PANs”).

Beyond traditional social networking features and services, a SNET group100 and associated fixed and intelligent services 102, socialdevices/resources 130 and other capabilities according to variousembodiments of the disclosure include numerous novel features andattributes as described more fully below and with general reference toFIG. 1. Briefly, in one embodiment of the disclosure, a variety ofconventional services and resources provided outside of SNET contextsmay be included (in addition to human and device members) in a SNETgroup or sub-group, including computing and networking devices,application software, databases, etc. Stated another way, such a SNETgroup may have member participants beyond humans. Such members mightcomprise, for example: networking elements such as network attachedstorage (NAS), firewalls, proxies, VPNs, etc.; media content storage orplayback and billing services; other database and storage backupservices; applications; human-like services such as an artificialintelligence “digital assistant”; DRM and security elements; supportfunctions specific to the group and/or the underlying membership; etc.Such members may have a fixed function or operate with an artificialintelligence “persona” or other intelligence capabilities. Further, anartificial persona or avatar that behaves as a friend or facilitatesSNET group usage or training might be selected to participate as amember. Such concepts may be extended to add an individual's“personification” overlay (video, appearance, voice, etc.) on top ofsuch persona/avatar, which may operate when the individual is offline.

For example, a SNET may offer a series of functional members that becomeavailable upon docking of a particular supporting device. Suchfunctional members may be visible and available across a user(s) SNETaccount, to a particular SNET group/circle, to the functional memberitself, to all SNET membership, etc. Note that many such elements andfunctionality (e.g., temporal alarms, security and contact managers,DMZ-type applications, etc.) are described or suggested herein. By wayof example, an application docked as a SNET group member may beconfigured automatically as a DMZ member with underlying functionality.In such an embodiment involving gaming activities, joinder of an SNETgroup by a gaming application and game member might result in serviceofferings to other SNET group members including, without limitation,configuration services based on underlying devicelimitations/capabilities. Similarly, docking of members may also triggermalware and virus scanning services within the SNET group, spanningthrough all (or a subset) of the implicated social devices, services,and software.

In another embodiment of the disclosure, payment authentication servicesare performed on a per-device (using a SIM card, bar code or the like)or per-SNET basis. For example, reading a bar code may triggerconnection with a social network providing various options, includingpayment options, and/or enable another SNET member (e.g., a familymember) to assume responsibility for payment of fines, fees, gamingcredits, etc. In this instance, an electronic invoice can be forwardedto the SNET and/or responsible SNET member, and payment may be conductedthrough (low power) Bluetooth or NFC-type functionality associated withan (SNET) electronic wallet, bank account, credit card, etc. Payment maybe subject to individual or circle-by-circle purchasing limits, andrequire one or more security/authentication steps. For example, a socialmember set-top box may incorporate smart/credit/debit card informationand an associated billing interface, element or application/applicationinterface to assist in performing billing transactions, includingtransactions involving confirmation via a separate communication pathwayand/or social member (a smart phone, for example). Purchasing, payments,crediting, receipts, etc., may be conducted and communicated within aparticular circle(s) via a circle/SNET member application or applicationinterface. Security and security proxy functions may also be integratedinto a social billing process according to the disclosure.

In another embodiment according to the disclosure, SNET group/circlemembers comprise “social” artificial intelligence functionality. Suchfunctionality may take the form, for example, of a dockable socialrobot. Potential applications include traditional (factory) robotmonitoring, program exchange and human-to-robot and robot-torobot-interaction via a SNET group (e.g., load sharing, supportactivity, data exchange, information, experience and training) Such anembodiment may be viewed as “inverting” the social network concept tocomputers/machines, and applying “friend” concepts, etc., for loadbalancing and collaboration in autonomous operating environments.

According to another embodiment of the disclosure, members within aSNET/circle may donate or expose personal device computational capacityor other resources (such as storage) to support a SNET managed process,such as distributed or peer-to-peer computing activities (for example,the search for extraterrestrial intelligence (SETI), virus decoding,etc.). Further, a SNET managed process may utilize accessible memberresources for distributed, real-time backup of each member's(distributed) data. Such distributed processes and associated data canbe limited to one or more SNET groups (such as a household social groupwith auto-docking), and may be utilized for a wide variety of otherpurposes such as control of a group of social “robots”, etc. Similarly,content or applications/software (e.g., imaging services) residing on adocked social device may be accessed by another social device.

Referring more specifically to FIG. 1, a social network circle/group 100(hereinafter “SNET circle” or “SNET group”) comprising fixed andintelligent social services 102 is shown. Briefly, membership in theSNET group 100 may comprise fixed and intelligent services 102, dockedsocial devices/resources 103 (embodiments of which are described inconjunction with FIGS. 7 and 17) and human SNET group members 104, aswell as proxies thereof. Further, SNET group 100 nodes may includedevice services and software (e.g., applications) of various typesparticipating as members. By way of example, SNET group members mightinclude artificial intelligence agents/social robots 106, SNET securitydevice(s) 108, appliances, vehicles and service providers 110, externalsocial device resources 112, common or authorized members/functionalityof other SNET groups, etc. Further, access to specific content andresources of a SNET group 100 may be shared with members of additionalSNET(s) 114, including remote or web-based applications. Such access canbe conditioned on acceptable profiling and association data. Similarly,social devices or individuals may be granted temporary or ad hocmemberships, with or without restricted access.

In the illustrated embodiment, formation, maintenance and operation ofSNET group 100 is performed by standalone or distributed SNET processingcircuitry and software 116. It is noted that the “SNET processingcircuitry” may comprise hardware, hardware and software, hardwaresupported software applications, or various combinations thereof, and beconfigurable to support various functionalities disclosed herein.Further, the SNET processing circuitry 116 may be included in astandalone server, server farm, cloud-based resources, and/or thevarious types of devices described below, and incorporate authenticationand security functionality 118. In addition, specialized middleware mayalso be utilized by SNETs according to the disclosure, includingstandardized middleware and/or standardized communication protocolshaving an associated certification process. Interactions andinterdependencies within the SNET group 100 may involve one or more ofan adaptive resource management, allocation and arbitration module 120,a social device association/control module 122, and a SNET group memberprofiling module 124.

As described more fully below, distribution of internal and externalSNET data content 126 can be accomplished in a variety of ways inaccordance with various embodiments of the disclosure. For example, datadistribution may involve an adaptive or parallel networkcommunication/routing infrastructure involving a wide variety ofcommunication protocols and wired and/or wireless communicationschannels, as well as one or more social devices/resources 130. SNET datacontent 126 may comprise, for example, various user-driven (advertising)channels, pictures, videos, audio communications, links, online text,etc. Access to such content, as well as communications with and remoteaccess to social devices 102 of the SNET group 100, may occur over anInternet backbone 128, cellular communication system, WAN, LAN, etc.

A member of a SNET in accordance with various embodiments of thedisclosure such as those disclosed herein may establish permissionsand/or privacy settings that control and restrict who or what may accessthe member's profile(s) information, offer services, communicationresources, connections and groups, as well as define desired degrees ofaccess. Permissions may enable the user to maintain certain resources orinformation as private or available on a permissive basis only. Forexample, accessibility to available communication resources or socialcontent may be limited to users/devices in a particular SNET or SNETgroup. Alternatively, such resources may be publicly available.Likewise, a SNET member may selectively decide to permit others toaccess personal information such as name, gender, contactinformation/email address, etc.

In the various embodiments, membership in a SNET group may be extendedto encompass public and private social devices and equipment. Forexample, in a SNET group that includes human members, each human membermay have a respective personal SNET sub-group of associated or dockedsocial devices capable of independent or aggregated participation in theSNET group. The SNET sub-group may be locally or remotely accessible bya human member and/or other SNET group/sub-group members through variousmeans, such as clicking on an icon or tag associated with the humanmember/personal sub-group. A SNET group may be persistent or of limitedduration, and include ad hoc and/or static associations.

Exemplary social devices may be broadly categorized as either (i) socialdevices that include a user or SNET group interface sufficient toprovide meaningful input to SNET interaction and (ii) social devicesthat support minimal or no user input relevant to SNET interaction. Moreparticularly and without limitation, the first category may includecomputers, tablet devices, IPTVs, IPTV set top boxes, smart phones,servers, laptops, cloudbooks, network attached storage devices, gamingconsoles, media players/sources, communication nodes (access points,routers, switches, gateways, etc.), user interface devices, power linecommunication (PLC) devices, etc. Such social devices may receive userinput for SNET setup and management. The second category may include,again without limitation, printers, projectors, cameras and camcorders,scanners, speakers, headsets, smoke detectors, alarm systems, videocameras, mice, etc. In general, dockable social devices include anyelectronic device that could be operably coupled to or docked in a SNETgroup/sub-group via wired or wireless pathways to participate as a SNETmember.

As will be appreciated, by docking social devices, members of a SNETcircle may gain full or partial remote control and interaction suchdevices via an authorized member SNET account. For example, familymembers authorized to participate in a “family” SNET circle may remotelyaccess docked social devices via one or more associated SNET accounts.Exemplary methods for docking and accessing social devices are describedmore fully below in conjunction with numerous of the Figures.

FIG. 2 illustrates an embodiment of a social group 202 comprising avariety of members in accordance with the present disclosure. In thisembodiment, membership in the social group 202 may include a variety ofnovel social system members 204 functioning in various capacities withinthe social group 202. As will be understood, certain of the socialsystem members 204 may support direct or indirect associations betweenthe social group 202 and human members/non-members and users 200.

In the illustrated embodiment, social system members (or nodes) 204include one or more local or remote servers and server clusters thatprovide a support infrastructure/supporting system for social groupfunctionality and member operations (routing, data storage, services,dockable services, etc.). Communications within the social group andwith non-members may occur via dedicated or multi-function communicationpath devices.

Social system members 204 further include devices configured to operateas nodes within the social group 202. Social functionality in suchdevices and other social system members 204 can be implemented throughvarious means. For example, a device may have integralhardware/firmware/software to support social group access and memberoperations. Alternatively, a general purpose device 204 a may includesocial code that enables participation in the social group 202. In afurther embodiment, a device 204 b designed to include socialfunctionality may participate in the social group 202 through acombination of non-social code and a social shim layer or driverwrapper. In yet another embodiment, a member device 204 c having asocial design may utilize additional social code, including codespecific to a social group 202.

Participation in the social group 202 is supported through functionalitythat includes automated and member-triggered membership invitations andprocessing (membership management) 206. More particularly, membershipmanagement 206 may function to invite prospective members to participatein the social group 202 through automatic, automated andmember-triggered processes. For example, membership management 206 mightbe configured by a human user 200 to establish a social group 202 byautomatically inviting/accepting social system members having certaincharacteristics (such as devices owned or controlled by the user oracquaintances of the user).

Processing of accepted invitations and unsolicited requests to join thesocial group 202 may be conditioned upon input or authorization from anexisting social system member(s) 204 or human user(s) 200 (e.g., througha user interface). Similarly, membership management 206 may beconfigured to generate automated suggestions regarding which prospectivemembers receive an invitation. Various other approaches, such as thosedescribed herein, can be used to establish membership in accordance withthe disclosure.

Access to and visibility of resources of a social group 202, includingservices and data, may be managed through general and memberclass-specific access configurations 208. For example, if membership inthe social group 202 includes family members and associated devices, auniform access configuration (or separate device and humanconfigurations) could be applied across the class in an automatic orautomated manner. In other embodiments, access control and constraints210 are imposed on a per-member basis.

The social group 202 may offer a wide variety of fixed and intelligentmember services 212, including both internal and external servicesaccessible by social system members 204. By way of example, the socialgroup 202 may offer payment processing services, storage and backupservices, robotic control functions, digital assistants, and otherservices (certain of which may themselves participate as members)between full members and/or authorized guest members and visitors. Incertain embodiments, member services 212 may themselves participate orbe selectable to participate as members of the social group 202. As withother resources of the social group 202, access control and constraintson member services 212 may be applied to individual members or classesof members.

FIG. 3 is a functional block diagram illustrating a social network(SNET) infrastructure 300 and (member) social device(s) 301 inaccordance with an embodiment of the disclosure. Communications betweenthe social network infrastructure 300 social device(s) 301 and otherSNET members may occur over one or more wired and wireless communicationnetworks 303. The SNET infrastructure 300 and social device(s) 301 arecoupled to the communication networks 303 by communication interface(s)331 and 311, respectively, either of which may support communicationswith individual SNET members or groups/classes of SNET members.

The SNET infrastructure 300 of the illustrated embodiment includes anumber of functions and resources to support formation and maintenanceof a SNET having social device (and/or service) members. In particular,member report management and processing 333 receives information fromSNET/group/member reporting functions 313 in associated social devices301. Such information may include, for example, status data 315regarding the location, address and activities of a social device 301and/or device user.

In addition, the social device 301 may provide device information 316indicating, for example, device functions and social capabilities,device model number(s), device configurations, software versions,attached peripherals and downstream (social) devices, device resourcesand usage, etc. Device information 316 relating to availableresources/services and current resource usage may be utilized by theSNET infrastructure 300 for purposes of SNET resource management,including dynamic resource allocation and arbitration.

In various embodiments, the social device 301 may have an obligation togather, store and/or report device status/information 315/316 atdifferent times. For example, reporting may be required upon affiliationor docking with a SNET, on a periodic basis, and/or during operationalengagements with other intra- and inter-SNET resources and devices(including upstream and downstream devices).

Referring again to the SNET infrastructure 300, additional functionalityand resources include, without limitation: SNET member informationcapture and storage management 334; a SNET application programminginterface (API) 335 that allows SNET associated software components tocommunicate with each other; security and access control management 337for maintaining the integrity of the SNET and affiliated data/resources;and (Web) server services 338. The social network infrastructure 300further comprises other group application services 305 corresponding tothe foregoing, as well as additional services such as those describedherein. In one exemplary embodiment, the SNET infrastructure 300 mightdetermine (e.g., by means of device information 316) the category andnature of a social device 301 wishing to participate in a SNET. Asnecessary, functionality in the SNET infrastructure 300 could thendirect or trigger installation of appropriate application software andunderlying drivers in the social device 301. Such operations might beperformed with minimal involvement from inherent functions of the socialdevice 301.

In the illustrated embodiment, the social device 301 comprises a numberof additional functions and resources to support participation in asocial network. More particularly, SNET, SNET and/or member controlfunctions 317 may include slave functions 318, master functions 319, andvarious combinations thereof. Slave functions 318 include, for example,device (re-)configuration, directed resource allocation, managedresource arbitration, bridging operations, etc. Master functions 319enable the social device 301 to establish, manage, and terminate variousinteractions between nodes or groups of nodes in a social network,including interactions involving the social device 301 itself.

The social device 301 further includes a social API 321 andbrowser-based interaction capabilities 327 to support, for example,relevant social applications and services 323 (which might compriseslave and master functions 318 and 319). Security and access control 325layers permit the social device 301 to interface with or establishsecure SNET groups/circles and control access to internal and externalSNET resources.

It is noted that numerous of the functional building blocks of theembodiment of the disclosure illustrated by FIG. 3 may be incorporated,in whole or part, in one or more (application specific) integratedcircuit devices. For example, an integrated circuit device may include amember reporting module to provide member reporting functionality(including communication of device status and device characteristics),device control capabilities, master/slave functions, security and accesscontrol modules, etc. Such an integrated circuit device may also includeonboard processing capabilities and/or interface with a processordevice. Alternatively, several of the functions described above may beincorporated, in whole or part, into an operating system and/or softwareloaded above an operating system kernel.

FIG. 4 is a functional block diagram of various embodiments of a socialnetwork group 429 offering fixed and intelligent services and networkelements in accordance with the disclosure. In the illustratedembodiments, standalone or distributed system circuitry such as SNETprocessing circuitry and software 400 manages formation, maintenance andoperation of SNET group 429, as well as provision and management ofaffiliated service and resource offerings. It is noted that the “SNETprocessing circuitry” may comprise local and/or remote hardware,software, applications, or various combinations thereof, and beconfigurable to support various fixed and intelligent services/resourcessuch as disclosed herein. Further, the SNET processing circuitry andsoftware 400 may be included in one or more processing systems, SNETinfrastructures, computers, (distributed) server devices, network nodes,cloud-based resources, social devices/services, or some combinationthereof. Likewise, SNET group 429 may be comprised of one or more SNETgroups/sub-groups.

SNET group 429 members, clients, users, and the like may include, forexample, human members of a SNET or some other network, authorizednonmembers of a SNET, guests of a SNET, device members of a SNET or someother network, certain fixed and intelligent services/resources, somecombination thereof, etc. In various embodiments, one or more servicesand capabilities associated with SNET group 429 may be accessed directlyor through interaction with the SNET group 429 (e.g., via supportingsystem and/or a tiered SNET grouping hierarchy such as described belowin conjunction with FIGS. 8-11). In addition, SNET group 429 may offer aseries of functional members and/or resources that become available upondocking of a particular supporting device. Such functional members maybe visible and available across a user(s) SNET account, to a particularSNET group/circle, to the functional member itself, to all SNETmembership, etc.

In various of the illustrated embodiments, for example, a variety ofservices and resources are enabled in a SNET group 429, including fixedand intelligent services 401, computing and networking elements 441, andsocial billing and payment elements 461. The SNET processing circuitryand software 400 of the illustrated embodiments include one or morehardware/software functions for managing and facilitating such servicesand resources. These functions may include, for example, fixed andintelligent service offering control capabilities 431 (which may includeconfigurable resource offering views, including visual offerings),distributed process management functions 433, DRM and billing managementcapabilities 435, resource management and access control capabilities437, membership management, docking and support services 438, andtracking and reporting functions 439.

A SNET group 429 according to the illustrated embodiments may supportand offer a wide variety of fixed and intelligent services 401. By wayof example, and without limitation, application software 403 may beoffered, including standalone applications (and associated devicedrivers as necessary) or dedicated applications that might support otherfunctions and resources of a SNET group 429. Other service offerings mayinclude storage and backup services 405, media-related services 407(content storage and playback, transcoding functions, billing and DRM,etc.), and communications services 409 (both intra- and inter-SNET).

In further embodiments according to the disclosure, SNET group 429membership and/or service offerings includes “social” artificialintelligence AI functionality 411. Such AI functionality may take theform, for example, of a dockable social robot. Potential roboticapplications (which may utilize other SNET group 429 resources includingrobotic controls 423 and robotic interfaces 453) include factory robotmonitoring, program exchange and human-to-robot and robot-torobot-interaction via a SNET group (e.g., load sharing, supportactivity, data exchange, information, experience and training) Furthersuch embodiments are described more fully below in conjunction FIG. 5.

AI functionality 411 in certain embodiments may include human-likeservices such as an artificial intelligence “digital assistant” 415 thatis docked as a member of SNET group 429 and supports functions specificto the group and/or the underlying membership. Such AI members may havea fixed function or operate with an AI “persona” or other intelligencecapabilities. Further, an artificial persona or avatar 413 that behavesas a friend or facilitates SNET group usage or training might beselected to participate as a member. Such concepts may be extended toadd an individual's “personification” overlay (video, appearance, voice,etc.) on top of such persona/avatar and, in certain embodiments, mayoperate when the affiliated individual is offline. SNET group membersmay interact with one another through such avatars, such as characterinteractions in a multi-user virtual gaming environment.

According to another embodiment of the disclosure, members or affiliatesof a SNET group 429 may donate or expose device computational capacityor other resources (such as storage) to support SNET managed ordistributed processes 417 and distributed processing/research 419, suchas distributed or peer-to-peer computing activities (for example, thesearch for extraterrestrial intelligence (SETI), virus decoding, etc.).In one embodiment, a SNET managed process may utilize accessible memberresources for storage and file transfer 421, including distributed orRAID-like, real-time backup of one or more member's (distributed) data,media content, etc. Such distributed processes and associated data canbe limited to one or more SNET groups (such as a household social groupwith auto-docking), and may be utilized for a wide variety of otherpurposes such as robotic control 423 of a group of social robots.Similarly, content or applications/software (e.g., imaging services)residing on a docked social device may be accessed by another socialdevice.

In a further embodiment, an application docked as a SNET group 429member may be configured automatically as a DMZ member with underlyingfunctionality, such as a guest member having access to some SNET groupresources but not others. For example, in an embodiment involving gamingactivities, joinder of an SNET group by a gaming application and gamemember might result in service offerings to other SNET group membersincluding, without limitation, configuration services based at least inpart on underlying device limitations/capabilities. Similarly, dockingof members may also trigger antivirus and malware detection services 427within the SNET group 429, spanning all (or a subset) of implicatedsocial devices, services, and software.

Network elements 441 may include, by way of example and withoutlimitation, network attached storage (NAS) 443, firewalls and VPNs 445,social or allocable communication resources 447,networking/communication proxies and gateways 449, security and DRMhardware/firmware 451, robotic interfaces 453, databases, etc. Suchresources may be allocated and utilized for specific purposes, or insupport of one or more services and distributed processes such as thosedescribed herein. Various approaches may be utilized for managing andallocating network elements 441 as well as services and other resources.Exemplary methods for access to social network offerings, includingthrough the use of general or member class-specific access rights, aswell as dynamic reallocation of resources, is discussed in furtherdetail in at least U.S. Utility patent application Ser. No. 13/408,986,entitled “Social Device Resource Management,” (Attorney Docket No.BP23776), filed Feb. 29, 2012, incorporated by reference herein in fullfor all purposes.

Various functions and resources of the social billing and paymentelements 461 may include, by way of example and without limitation, asmart/digital electronic wallets 463, invoicing/billing interfaces 465,tracking and reporting functions 467, proxy functions 469, NFC/Bluetoothsupport 471, transaction security functions 473, etc. In one exemplaryembodiment of the disclosure utilizing various of social billing andpayment elements 461, payment authentication services are performed on aper-device (using a SIM card, bar code or the like) or per-SNET basis.For example, reading a bar code may trigger connection with a socialnetwork providing various options, including payment options, and/orenable another SNET member (e.g., a family member or processing node) toassume responsibility for payment of fines, fees, gaming credits,spending limits, etc. In this instance, an electronic invoice can beforwarded to the SNET group and/or responsible SNET member, and paymentmay be conducted through NFC-type functionality associated with an(social) electronic wallet, bank account, credit card, etc.

Payment may be subject to individual or circle-by-circle purchasinglimits, and require one or more security/authentication steps. Forexample, a social member set-top box may incorporate smart/credit/debitcard information and an associated billing interface, element orapplication/application interface to assist in performing billingtransactions, including transactions involving confirmation via aseparate communication pathway and/or social member (a smart phone, forexample). Purchasing, payments, crediting, receipts, addition of creditsand awards, etc., may be conducted and communicated within a particularcircle(s) via a SNET member application or application interface.Security and security proxy functions may also be integrated into asocial billing process according to the disclosure.

As will be appreciated, a SNET group 429 may be configurable to performand utilize a wide variety of functions and services, including bothmember and non-member services, and selection of such services for useby a particular SNET group 429 may occur in a variety of ways. By way ofexample, a member device may offer a menu of available services to anaffiliated human for use in selecting (local or remote) services fordocking as a group member or otherwise activating and/or configuringservices. Alternatively, services themselves, including member servicesor cloud-based services, might generate an invitation that can beaccepted by one or more SNET group 429 members or affiliates. In otherembodiments, a device that incorporates a social service (e.g., a socialdevice purchased by a human member of an SNET group) can be activatedand docked as a member of an SNET group, thereby making the socialservice available to other group members and affiliates. Alternatively,a service incorporated in a device—rather than the full device—may bedocked with a SNET group.

Further, a social service in accordance with the disclosure may havemultiple portions that run on different nodes of an SNET group or SNETsupport infrastructure. Using a media streaming service as an example, aportion of such service may operate on a docked social device (e.g., adevice with media display capabilities), while other portions of theservice, such as storage, billing or menu functions, may run on otherSNET group nodes such as a NAS device 443 or social billing and paymentelement 461. The media streaming service may incorporate or operate inconcert with other services, including external or third party services,such as a transcoding service that scales video for consumption by avariety of devices. Such video might be offered, for example, via amulti-port STB/gateway (such as that described in conjunction with FIG.6) that maintains IP address information, linkages, deviceconfigurations, etc., and may deliver video via a direct or proxiedcommunication pathway.

FIG. 5 is a functional block diagram of an artificial intelligence(AI)/robotic SNET group 500 in accordance with the disclosure. Variousembodiments of the SNET group 500 may include a wide variety ofsocial/dockable robotics and AI agents 506, including, for example,discrete and/or distributed robots or robotic manufacturing equipment,robotic controls and monitoring services and machinery 508, componentsof one or more (physical or logical) assembly lines 510-512, proxies516, medical equipment, etc.

In the illustrated embodiment, operation of the AI/robotic SNET group500 is supported by SNET infrastructure 501, including social roboticinterfaces, support and processing 502 to support, for example,human-to-robot and robot-to robot-interaction, factory robot monitoring,etc. Further, the AI/robotic SNET group 500 incorporates or supports avariety of intelligent services 504, including training andcustomization services 520, data and program exchange services 522,software maintenance services 524, load balancing and arbitrationservices 526, security functionality 528, membership and docking support530, etc.

In certain embodiments, such services may be used to establish,configure and maintain, for example, robotic and other configurableproducts, robotic manufacturing, assembly or other specializedprocesses. Select services also provide for: the cloning ofsoftware/hardware configurations and data exchange to facilitate setupand replication of robotic processes and activities; experience andtraining sharing (e.g., neural networking enhanced processes); resourceallocation and load balancing; control, monitoring, support, andhardware/software maintenance operations; etc.

Various nodes and elements of the AI/robotic SNET group 500 may sharefunctional control of robotic and AI activities and/or interact with acentral control point (e.g., robotic controls and monitoring 508). Forexample, human members 514 or proxies 516 thereof may direct operationof SNET group functions and/or be the subject of such functions.Authorized access to services and resources of the SNET group 500 can befacilitated through unique biometric identifiers, passwords, token-basedidentification, trusted authorities or documents such as a driver'slicense or passport, and like authentication means.

Other entities may also interact with the AI/robotic SNET group 500including, by way of example, vehicle manufacturers, automobile owners,hospitals and medical providers, repair shops, insurance companies,governmental inspection and compliance agencies, emergencyservices/devices, and other third parties that might have an interest incommunicating with or participating in the AI/robotic SNET group 500. Inanother embodiment, an AI/robotic SNET group 500 may itself join anotherSNET group, or form one or more SNET sub-groups. In various embodiments,AI and robotic elements of the SNET group 500 may operate as socialdevices, social “parent” devices and social “child” devices as describedbelow in conjunction with FIGS. 6 and 7, including functioning as achild/parent for one or more human members 514.

FIG. 6 is a schematic block diagram of an embodiment of a social set-topbox (STB)/gateway in accordance with the disclosure. The STB/gateway 601provides a number of functions, including conversion of signals fromupstream sources into content that can be consumed by downstream socialdevices and services. The STB/gateway 601 may further operate as agateway that supports unidirectional or bidirectional communications andbridging between upstream and downstream devices and services.

As described more fully in conjunction with FIG. 7, the illustratedsocial devices (or, alternatively, services) may operate in a socialdevice “hierarchy” comprising social devices, social “parent” (SP)devices and social “child” (SC) devices. Briefly, SP devices may enableassociated SC devices to interact and/or connect with a social network,either directly or indirectly. Social capabilities of a SC device can beprovided via a SP device.

Further, certain social devices according to various embodiments andapplications of the disclosure, such as the STB/gateway 601 anddownstream devices 641-649, may concurrently or selectively function asa social device, SP device, and/or SC device. Associations between SPand SC devices may be established in a selective, automatic or automatedmanner. For example, docking of the STB/gateway 601 with a SNETinfrastructure 605 may result in automatic docking of user(s) homedevices.

The STB/gateway 601 of the illustrated embodiment interacts with a SNETinfrastructure 605 and (SNET) external media systems 607 via one or morewired and wireless networks/links 603. The wired and wirelessnetworks/links 603 (and 609) may utilize one or more of varioustransmission media—such as coaxial cable, shielded twisted pair cable,fiber-optic cable, power line wires, and wireless media (radiofrequencies, microwave, satellite, infrared, etc.)—and operate inaccordance with a variety of communication and networking protocols(TCP/IP, UPnP, IPv6, etc.). In addition, the wired and wirelessnetworks/links 603 may comprise a multi-hop network utilizing a spanningtree protocol, direct wireless connections, peer-to-peer links, etc.

The (SNET) external media systems 607 may comprise, for example, one ormore of cable, satellite and/or terrestrial televisions systems. Variousheadend equipment and services can be utilized by these systems, such asa cable headend that receives television signals for further processingand distribution, and may offer various other services such as internetconnectivity.

While the illustrated STB/gateway 601 functions as a social parentdevice, in alternate embodiments it could have a peer-to-peer or parentrelationship with the SNET infrastructure 605 (and SNET membersassociated therewith) or (SNET) external media systems 607. For example,a cable headend itself might include social capabilities allowing it toparticipate as a node in a social network.

The STB/gateway 601 of the illustrated embodiment includes abroadcast/unicast/multicast front end 613 that operates to receivecompressed digital video, digital audio and other data signals, fromeither the (SNET) external media systems 607 or SNET infrastructure 605,for further processing and distribution. The front end 613 comprisestuner circuitry 619 a operable to isolate particular channels. Signalsfrom the tuner circuitry 619 a are then provided to analog-to-digital(ADC) circuitry 620 a and demodulation circuitry 621 a for conversioninto binary format/stream. Once in binary format, forward errorcorrection (FEC) circuitry 622 a checks the integrity of the receivedbinary stream. Audio, video, and data extracted from the binary streammay then be decoded (e.g., by decoding 625) into formats suitable forconsumption by downstream social devices. It is noted that demodulationcircuitry 621 a may support one or more modulation techniques, such asQuadrature Phase Shift Keying (QPSK), Quadrature Amplitude Modulation(QAM), Coded Orthogonal Frequency-Division Multiplexing (COFDM), etc.

The front end 613 may be integrated into one or more semiconductordevices that may further support, for example, interactive digitaltelevision, networked DVR functionality, IP video over DOCSISapplications, and 3D graphics support. In addition, multiple tunercircuitry 619 a (including in-band and out of band tuners), ADCcircuitry 620 a and demodulation circuitry 621 a may be provided fordifferent television standards (such as PAL, NTSC, ATSC, SECAM, DVB-C,DVB-T(2), DVB-H, ISDB, T-DMB, Open Cable) and modulation schemes.Further, in certain embodiments, sharing of channels and associatedprogram information provided by the front end 613 may be considered asocial function.

In one alternative embodiment of the disclosure, functionality of theSTB/gateway 601 functionality is performed by a smartphone or mobilecomputing device. In this embodiment, the “front end” 613 comprises oneor more wireless interfaces (including PHY and baseband functions), suchas a cellular (3G, 4G, IMT-Advanced, etc.) or wide area network (WiMax,etc.) interface. The interface may support one or more modulation andmultiplexing techniques, such as OFDM, OFDMA, SC-FDMA, QPSK, QAM, 64QAM,CSMA, MIMO, etc. In the illustrated embodiment, the wireless interfacecomprises a transceiver 619 b, analog-to digital (ADC) anddigital-to-analog (DAC) circuitry, demodulation and modulation circuitry621 b and FEC (such as turbo codes or LDPC codes) circuitry 622 b.Encoding, decoding and transcoding 625 functions may be provided byprocessing circuitry 611.

The STB/gateway 601 also includes upstream social communicationinterface circuitry 615 for communicating with SNET infrastructure 605and/or (SNET) external media system 607. Through the socialcommunication interface circuitry 615, the STB/gateway 601 maycommunicate directly with upstream resources, or offer (bidirectional)bridged communications between such resources and devices (e.g., socialdevices 641-649) coupled to the STB/gateway 601.

In the embodiment of FIG. 6, STB/gateway 601 interacts with a variety ofsocial devices 641-649 and upstream resources via upstream socialcommunication interface circuitry 615 and downstream social “child”communication interface circuitry 617 coupled to one or more wired andwireless communication networks 603/609. For example, a televisioninterface module 631 communicates with a (digital) television 641 orother media display device to relay television programming and enableavailable interactive services. Similarly, an audio interface 633provides audio programming or audio library access to an audio system643.

The communication interface circuitry 617 further comprises a remotecontrol interface 635 for receiving control signals from a remotecontrol 645. In addition to traditional remote control operations, theremote control 645 may further offer voice and/or gesture controlsignals that are relayed or mapped to relevant consumer devices. Userinterfaces 637 are also provided for communications with one or moreuser interface devices 647. Gaming interfaces 639 function to provideinteractive communications with a gaming system 649. Such communicationsmay involve, for example, online, multiplayer gaming between members asocial network and/or external players in a gaming platform.

Various communications between downstream devices 641-649 may bebridged, without substantive modification, to various nodes in a socialnetwork via social bridging interfaces 640. Such bridging may operateindependently of the set top functionality of the STB/gateway 601. Forexample, social child devices may communicate directly with a SNETinfrastructure 605 to receive “social” channel broadcasts from a socialgroup or IPTV services.

The STB/gateway 601 of the illustrated embodiment includes processingcircuitry 611 (which may be comprised of hardware, software, orcombinations thereof), social upstream/downstream functionality support623, and decoding functionality 625 to support social interactions suchas those described above. Social upstream/downstream functionalitysupport 623 in this embodiment includes various functions such as socialbridging 627, parent-child services 629, and other functionality such asfunctions 313-327 of FIG. 3. It is noted that the processing circuitry611 may be made available in whole or part as a SNET resource.

Referring now to FIG. 7, a schematic block diagram is shown for a socialdevice 701 operable to support various interactions between other socialdevices and social services and systems in accordance with an embodimentof the disclosure. The social device 701 is configured with a variety offunctions that enable it to operate in a social device hierarchycomprising social (S) devices, social “parent” (SP) devices and social“child” (SC) devices. For example, a social parent device may enable adocked social child device to access resources of the parent deviceand/or connect to and interact with (directly or indirectly) with asocial network. The social child device may be configured with inherentsocial capabilities, or gain access to such capabilities from or throughan associated parent device. Further, a human SNET member might haveassociated social child devices, or be served by a social parent devicevia a user I/O interface (723).

A social device 701 according to various embodiments and applications ofthe disclosure may also concurrently or selectively function as a socialdevice, SP device, SC device, or even a “grandparent” device thatsupports (e.g., in a multi-hop environment) a parent device in a SNETgroup. Dynamic and static hierarchical associations between SP and SCdevices may be established in a selective, automatic or automatedmanner. Further, a social device 701 may take many forms including,without limitation, a smartphone, personal computer, server, tabletdevice, access point, gateway, network switch/hub, bridging device, settop box, or other device enabled with social capabilities.

In the illustrated embodiment, the social device 701 is communicativelycoupled to a SNET infrastructure 709 and/or social parent system 711 viaupstream social communication interface circuitry 707. Likewise,downstream social peer and/or child communication interface circuitry713 enables coupling with a social child device 715, social peer device717 and/or social parent system (device) 719. Social resources of bothupstream and downstream devices may be accessible to one another via thesocial device 701.

The social device 701 of this embodiment includes social resources 703that, along with external SNET resources, are managed by a socialresource management module 705 and accessible to at least one other SNETgroup member. Specific social resources 703 may include user I/Ointerfaces 723, general purpose and dedicated hardware processingcircuitry 724, peripheral circuitry and components 725 (which may or maynot have social capabilities), communication bandwidth and creditdetermination functionality 726 (e.g., for use by payment processingservices), switching/bridging functions 727, application software andfixed/intelligent services 728, remote social resources 729 of the SNETgroup, external social resources 731 controlled by the social device701, etc. The external social resources 731 may comprise, for example,an external data/digital library, or content from one or more of cable,satellite and/or terrestrial televisions systems.

Among other functions, the social resource management module 705comprises access, allocation, arbitration and scheduling functionality721, as well as the functionality for establishing, regaining andrelinquishing control processing operations 722, including operationsinvolving access to social resources 703. It is noted that counterpartsocial resource management functionality may be present in the SNETinfrastructure 709 and/or other SNET nodes.

In one exemplary embodiment wherein the social device 701 comprises aswitching bridge, bandwidth capacity may be dynamically allocated byaccess, allocation, arbitration, and scheduling functionality 721.Access to bandwidth capacity and other resources of the social device701 might be available only upon request, per access views, or perallocation and arbitration functions, and selectively terminated whenexcessive bandwidth/resources are consumed or requested.

FIG. 8 illustrates a schematic block diagram of a social networkinggrouping hierarchy 800 according to various embodiments of thedisclosure. In some embodiments, a SNET grouping hierarchy 800 includesone or more tiers of SNET infrastructure, encompassed at least in partby a SNET, that can be docked to (hereinafter referred tointerchangeably as “associated with”, “joined”, and the like) other SNETinfrastructure, SNET groups, and social devices. For example, in theillustrated embodiment, one tier of SNET grouping hierarchy 800 caninclude a service SNET infrastructure 801, and another tier of SNETgrouping hierarchy 800 can include one or more client SNETinfrastructures 803, 805, and 807. In some embodiments, various tierscan be docked such that a “higher” tier can be docked to “lower” tiersto provide access by “lower” tiers to various capabilities provided bythe “higher” tier.

In some embodiments, one or more infrastructures are managed by one ormore processing systems, computers, server devices, network nodes,social devices/services, or some combination thereof. For example, inthe illustrated embodiment, some or all of the service SNETinfrastructure 801, one or more client SNET infrastructures 803, 805,and 807, or some combination thereof may be managed by one or moresocial service support devices 811, one or more client social devices831, 841, and 851, or some combination thereof. Processing systems caninclude, without limitation, one or more instances of processingcircuitry distributed across one or more server devices or networknodes.

For example, in the illustrated embodiment, SNET grouping hierarchy 800includes a service SNET infrastructure 801 in a first tier, and multipleclient SNET infrastructures 803, 805, and 807 in a second tier.Infrastructures can include, without limitation, one or more SNETgroups, one or more services, applications, resources, devices, and thelike associated with one or more entities, which can include, withoutlimitation, clients, members of a SNET, nonmembers of a SNET, guests ofa SNET, etc. For example, service SNET infrastructure 801 may includeuser devices 811, applications 813, and SNET groups 815, 817, and 819associated with one or more services.

Similarly, a client SNET infrastructure 803 can include one or moreclient SNET groups 835 and one or more social devices 831 associatedwith one or more particular clients (hereinafter referred tointerchangeably as users, members, visitors, guests, and the like). Forexample, a first client-side infrastructure 803 can include one or moreSNET groups 835 associated with a SNET member, along with one or moresocial devices 831 associated with the SNET member. As shown in theillustrated embodiment, the social devices 831 in a clientinfrastructure 803 can be docked or otherwise affiliated with SNETgroups associated with the client. At least one process of docking isdiscussed in further detail in at least U.S. Utility patent applicationSer. No. 13/408,986, entitled “Social Device Resource Management,” filedFeb. 29, 2012, incorporated by reference herein in full for allpurposes. In some embodiments, a device or SNET group docked to anotherSNET group becomes a member of the SNET group to which it is docked. Bydocking a client social device 831 to a client SNET group 835, a userassociated with a client SNET group 835 may interact with the SNET group835 by interacting with a social device 831 docked to the SNET group835. Members, clients, users, and the like may include, withoutlimitation, human members of a SNET or some other network, devicemembers of a SNET or some other network, certain fixed and intelligentservices, some combination thereof, etc.

In some embodiments, one or more capabilities which might include, forexample, various services, applications, or SNET groups, are mixed,combined, and/or merged via a docking process, into one or more SNETgroups that can provide access to a desired selection of capabilitiesthrough interaction with the one or more SNET groups. For example,service SNET infrastructure 801 illustrates capabilities that can beprovided by various service support social user devices 811 and/orvarious social servicing applications 813. In some embodiments, accessto various service support social user devices 811, either directly orthrough interaction with a SNET group 815 to which the service supportsocial user devices 811 are docked, and access to various socialservicing applications 813, either directly or through interaction witha SNET group 819 docked to the social servicing applications 813, can beprovided to SNET members.

One or more of the capabilities provided by the devices 811,applications 813, and SNET groups 815 and 819 may be combined into asingle SNET group that can provide access to one or more capabilitiesprovided by devices, services, applications, SNET groups, or somecombination thereof. For example, a user of a client SNET infrastructure803 can, by docking a social device 831, via a docking process 825(which may be supported by local or distributed system circuitry), to asingle SNET group 817 that itself combines SNET groups 815 and 819, gainaccess to the capabilities provided by both SNET groups 815 and 819 bydocking with SNET group 817.

In some embodiments, access to capabilities provided by one or more SNETgroups/infrastructures can be accomplished by docking one SNET group toanother SNET group. For example, a client SNET group 835 can be docked,via a docking process 825, to SNET group 817, thereby enabling a user ofthe client-side infrastructure 803 to access the capabilities providedby SNET group 817 through the client SNET group 835. In particular,where one or more social devices 831 are docked to the client SNET group835, a user can access the capabilities provided by SNET group 817 viaone or more of the social devices 831 that are docked with the clientSNET group 835. A docking process 825 can include joining client SNETgroup 835 as a member of SNET group 817, docking (also referred toherein as “associating”) client SNET group 835 to SNET group 817 via oneof various processes described herein and in at least U.S. Utilitypatent application Ser. No. 13/342,301, entitled “Social Network DeviceMemberships and Applications,” filed Jan. 3, 2012, and U.S. Utilitypatent application Ser. No. 13/408,986, entitled “Social Device ResourceManagement,” filed Feb. 29, 2012, incorporated by reference herein infull for all purposes.

As an illustration of the above embodiment, a user entering premisesincluding, without limitation, a store, restaurant, hotel, business,public area, and the like may desire to access capabilities including,without limitation, services, applications, information, devices, somecombination thereof, and the like provided by a SNET group associatedwith the premises. Rather than individually dock each of the user'sdevices with the SNET group, the user can simply dock a personal SNETgroup, to which the user's devices are docked, with the SNET groupassociated with the premises, thereby granting the user access to thepremises' capabilities through some or all of the devices that the userhas docked with his personal SNET group. As a further example, a hotelmay provide various capabilities including, without limitation, accessto a call routing phone service, control of a particular televisiondevice, access to a database, payment and billing services, etc. througha SNET group. Rather than individually dock his personal devices to thehotel's SNET group to utilize the capabilities provided, including, forexample, docking a smartphone device to the hotel SNET group to utilizethe call routing phone service, or docking a computer device to thehotel SNET group to control the particular television device, the guestcan simply dock his personal SNET group to the hotel's SNET group andthen access the capabilities provided through the hotel's SNET groupthrough a device docked with his personal SNET group.

In some embodiments, docking SNET groups such that a user, member,client, or the like can access capabilities provided by variousservices, devices, and SNET groups associated with various SNETinfrastructures enhances security. For example, where a user associatedwith a first client SNET infrastructure 803 can only access capabilitiesprovided by service SNET infrastructure 801 by docking with SNET group817, various levels of security can be utilized by one or moreprocessing systems/devices associated with the service SNETinfrastructure 801, client SNET infrastructure 803, etc. to ensuresecure access to the capabilities.

In addition, in some embodiments, accessing capabilities provided by aSNET infrastructure by docking two or more SNET groups providesadditional levels of security. For example, where access to capabilitiesprovided by service SNET infrastructure 801 entails docking a clientSNET group 835, 845, 855, or the like to SNET group 817, a more secureconnection, with various levels of security, can be employed, and accessto the capabilities can be easily granted, altered, restricted, orterminated via management of a single dock or association between aclient SNET group and SNET group 817. A processing system/deviceassociated with the service SNET infrastructure 801 or a client SNETinfrastructure 803 may manage the association based upon inputs receivedfrom a user, a third-party entity, some internal logic, elapse of aperiod of time, a change in geographic location of a client socialdevice 831 associated with the client SNET infrastructure 803, or someother trigger event.

In some embodiments, the selection and docking process 825 can beautomated, and/or automatic. For example, a docking process may beautomatic by being triggered based upon a location of a user of aninfrastructure, including, without limitation, a geographic proximity ofone or more of a user, a social device 831 associated with a user, or asocial device 831 docked with a particular client SNET group 835. Insome embodiments, a user can provide one or more association rules thatcan provide conditions under which one or more particular client SNETgroups 835 can be docked to other SNET groups. Conditions may include,for example, geographic proximity of one or more social devices 831docked to the particular client social 835 to a geographic locationassociated with a SNET group 817, authorization by a user associatedwith the infrastructure 803, SNET group 835, or social device 831 todock the client SNET group 835 with SNET group 817. Association rulescan be communicated to a social device 831 docked with a particular SNETgroup 835 or a processing system that manages docking of various SNETgroups. A processing system, a social device 831, or some combinationthereof can monitor a client SNET group 835, social device 831 docked tothe client SNET group 835, one or more attributes of another one or moreSNET groups 817 in relation to one or more attributes of one or moreclient SNET groups 835, docked social devices 831, or the like inrelation to one or more association rules in order to determine whetherto dock one or more SNET groups and/or social devices/services together.Association rules can be altered by a user or a processing system on thefly to create new rules, delete rules, alter rules, etc. For example, auser associated with a client SNET group 835, who may have previouslycommunicated to a processing system an association rule that prohibitsdocking the client SNET group 835 to a SNET group 817 beyond a thresholdgeographic proximity to a social device 831, can communicate, on thefly, an alteration of the association rule that can include, forexample, altering the threshold geographic proximity, authorizing adocking of the client SNET group 835 to a particular SNET group 817 on acase-by-case basis, ordering an undocking of a client SNET group 835from another SNET group, etc.

In some embodiments, various tiers of a SNET grouping hierarchy 800 aresubject to various levels of access to information and/or services. Forexample, in the illustrated embodiment, a user of the “higher-tier”service SNET infrastructure 801 may be able to view each client SNETgroup 835, 845, and 855 associated with a “lower-tier” client SNETinfrastructure 803, 805, and 807 that is docked to a SNET group 817associated with the social service infrastructure 801. A user of theservice SNET infrastructure 801 may also be able to view the varioussocial devices 831, 841, and 851 docked to the various client SNETgroups 835, 845, and 855. In another example, one or more users of a“lower-tier” infrastructure including, without limitation, client SNETinfrastructure 803, 805, and 807 may be able to view some or all of thecapabilities provided through a SNET group associated with a“higher-tier” infrastructure to which a SNET group associated with the“lower-tier” infrastructure is docked, but cannot view some or all ofthe “higher-tier” infrastructure, including, without limitation, variousSNET groups 815 and 819 from which capabilities provided by SNET group817 are originally provided. Additionally, a user of a “lower-tier”infrastructure accessing a SNET group 817 associated with a“higher-tier” service SNET infrastructure 801 may be unable to view someor all of the other similarly “lower-tier” client SNET infrastructures805 and 807 that are also docked with the same SNET group 817.

In some embodiments, the selection and docking process 825 can becontrolled or managed by one or more various social devices orprocessing systems. For example, a processing system of a SNETinfrastructure, which can include one or more instances of processingcircuitry distributed across one or more server devices and/or networknodes may control the docking and undocking of one SNET group toanother, based upon a user's interaction with the SNET, one or moreassociation rules, one or more inputs, some internal logic, etc. Asanother example, a social device may control the docking and undockingof one or more SNET groups based upon a user's interaction with theSNET, one or more association rules, one or more inputs, some internallogic, etc. In some embodiments, a processing system or social deviceauthorized to manage a “higher tier” infrastructure can manage one ormore attributes of access by one or more “lower-tier” infrastructuresdocked to the “higher-tier” infrastructure. For example, a processingsystem authorized to control a “higher-tier” social serviceinfrastructure 801 may alter access to certain capabilities, restrictaccess to certain capabilities, and/or terminate access via undocking ofSNET groups and devices based upon input or other logic operation. Theprocessing system may determine that a trigger event (e.g., all socialdevices 831 docked with a client SNET group 835 docked to SNET group 817have exceeded a predetermined threshold of proximity distance from ageographic location associated with SNET group 817) has occurred and,based upon the determination, undock the client SNET group 835 from SNETgroup 817, partially or fully restrict access by client SNET group 835to certain capabilities provided by SNET group 817, etc.

Referring now to FIG. 9, representative resource views according tovarious embodiments of the disclosure are illustrated. In someembodiments, a user, SNET member, or SNET nonmember associated with afirst infrastructure that is docked with a second infrastructure (viaone or more docked SNET groups or social devices/services) can accesscapabilities provided by the second infrastructure by interacting with arepresentative view. The representative view can be part of dataprovided by a processing system, some part of the second infrastructure,some part of the first infrastructure, a social device associated withthe first infrastructure, a second device associated with the user, somecombination thereof, or the like. For example, where a client SNET group835 of the first social client-side infrastructure 803 is docked with aSNET group 817 of the social service infrastructure 801 that providesdevice access capabilities 811 and 813 (provided by SNET groups 815 and819), a user may access capabilities provided by SNET group 817 viainteraction with a representative view 901. Where a client SNET group835 is docked with one or more client social devices 831, a user mayinteract with some part of one or more social devices 831 to accesscapabilities provided by SNET group 817 via the client SNET group 835,directly via the social devices 831, etc.

In some embodiments, a representative view can provide a simplifiedrepresentation of the services and other capabilities that can beaccessed via a docking of one or more SNET groups or devices. Forexample, while SNET group 817 provides capabilities 811 and 813 bymerging the SNET groups 815 and 819, a representative view 901 providedto a member accessing SNET group 817 (e.g., via a docked client SNETgroup 835 or AI agent/proxy node 905) may display only the capabilitiesprovided by SNET group 817 with little or no indication of the truecomplexity of the groups 815 and 819 that are combined to enable SNETgroup 817 to provide capabilities 811 and 813. A member accessing thecapabilities 811 and 813 via a representative view 901 may access thecapabilities 811 and 813 by interacting with representations of thosecapabilities included in representative view 901. Interaction with therepresentative view 901 can, in some embodiments, proceed viainteraction with some part of a docked social device 831 including,without limitation, a user interface, service or a part of a dockedclient SNET group 835.

In some embodiments, one or more third-party SNET groups associated withseparate members, infrastructures, and the like are docked with a firstSNET group to enable members of the third-party SNET group to accesssome or all of information and resources/services associated with thefirst SNET group. For example, in the illustrated embodiment, an AIagent/proxy 905 can be docked to client SNET group 835, thereby enablingaccess to some or all of the information provided to members of clientSNET group 835, capabilities provided by SNET group 817 that is dockedto client SNET group 835, etc.

As an example of the above, a traveler may desire to dock a client SNETgroup or agent/proxy 905 associated with his company to a personalclient SNET group 835 associated with his business travels. By dockingin this manner, the traveler may enable members of the company'sagent/proxy 905 to view the traveler's whereabouts provided to membersof his personal client SNET group 835, access at least some of thecapabilities provided to the traveler by docking with other SNET groupsvia the same or a similar representative view 901 (e.g., access andmanage his travel reservations, provide relevant travel and businessupdate information to the traveler on the fly, etc.), etc. Such dockingscan be managed by the traveler's social device 831, by the socialservice infrastructure 801 based upon input provided by the traveler, byone or more other devices or services, or some combination thereof. Forexample, the traveler may authorize only limited access by dockedthird-party AI agents/proxies 905 to information associated with hispersonal client SNET group 835, to services and other capabilitiesprovided by a docked SNET group 817. Further, the traveler may authorizeaccess restrictions, undocking, and like operations based uponon-the-fly input or one or more trigger events. Trigger events caninclude, without limitation, a change in geographic location associatedwith one or more social devices 831 associated with the traveler, achange in authorization information provided by an entity, etc.

In some embodiments, distinct representative views can be provided whereseparate SNET groups and/or SNET services and devices associated with a“lower-tiered” infrastructure are docked to a “higher-tiered”infrastructure in a SNET grouping hierarchy. In the illustratedembodiment, for example, client SNET group 835 and client SNET group855, which are associated with a first social client-side infrastructure803 and an Nth social client-side infrastructure 805, respectively, areeach docked to SNET group 817 associated with social serviceinfrastructure 801. In the illustrated embodiment, a firstrepresentative view 901 is provided to a member accessing thecapabilities of SNET group 817 through the client SNET group 835, adocked social device 831, and/or AI agent/proxy 905, and an nthrepresentative view 903 is provided to a member accessing thecapabilities of SNET group 817 through client SNET group 855, a dockedsocial device 851, or some combination thereof.

In some embodiments, representative views provided to separate dockedSNET groups are distinct and separate. For example, in an embodimentwhere SNET group 817 provides capabilities associated with a hotelexperience, including, without limitation, remote control of atelevision device or payment services, and wherein docked client SNETgroups 835 and 855 are associated with separate hotel guests, thecapabilities provided via one or more separate representative views canbe distinct such that the hotel guest can access capabilities customizedto the guest. Where the guest is not a SNET member, the guest can beinvited to create a temporary/guest SNET group or an ad hoc SNET group,and then dock the created SNET group to another SNET group to accesscapabilities provided by the other SNET group.

Referring now to FIG. 10, a social networking grouping hierarchy 1000and representative resource views 1005 according to various embodimentsof the disclosure are illustrated. The SNET grouping hierarchy 1000 canenable a client SNET group, AI agent/service and/or proxy 1035 (“clientSNET group 1035”) to dock to a SNET group that provides capabilitiesfrom various infrastructures. In the illustrated embodiment, twoinfrastructures 1001 and 1003 are combined, docked, or otherwiseassociated to provide capabilities from both through a single combinedSNET group 1037. The global social service infrastructure 1001 includescapabilities provided by social service support user devices 1011,social servicing applications 1013, and various SNET groups 1015, 1019,and 1017 that provide some combination of the services and othercapabilities provided by the infrastructure 1001.

In addition, the local/regional social service infrastructure 1003 alsoincludes capabilities provided by social service support user devices1021, social servicing applications 1023, and various SNET groups 1025,1029, and 1027 that provide some combination of the services and othercapabilities provided by the infrastructure 1003. The combinedlocal/regional and global SNET group 1037 provides a combination of thecapabilities provided by the social service support user devices 1011and 1021 and the social servicing applications 1013 and 1023 provided byboth infrastructures 1001 and 1003. Where client SNET group 1035 can bedocked with SNET group 1037, a member of client SNET group 1035 will beable to access the capabilities provided by both infrastructures bydocking a single client SNET group with a single SNET group 1037.

In some embodiments, a representative view 1005 provided to a member ofclient SNET group 1035 accessing the capabilities provided by SNET group1037 includes only the combined capabilities provided by bothinfrastructures 1001 and 1003 independently of some or all indicationsof the infrastructure from which such capabilities are originallyprovided. In the illustrated embodiment, for example, the capabilitiesprovided by the social service support user devices 1031 and 1021 fromboth infrastructures 1001 and 1003 are presented in the representativeview 1005 as a combined set of social service support user devices 1031;likewise, the social servicing applications 1013 and 1023 from bothinfrastructures 1001 and 1003 are presented in the representative view1005 as a combined set of social servicing applications 1033. Inaddition, all of the SNET groups 1015, 1017, 1019, 1025, 1027, and 1029in the infrastructures that are partially or fully combined into SNETgroup 1037 may be partially or fully transparent to a member accessing arepresentative view 1005 of the capabilities provided by SNET group1037. In some embodiments, a member accessing representative view 1005can restore the full complexity of the combination of infrastructures1001 and 1003 in representative view 1005, such that the member can viewthe various SNET groups and capabilities specific to variousinfrastructures and provided capabilities.

As an example of the illustrated embodiment, a hotel chain may provide aglobal SNET infrastructure 1001 that provides capabilities common to allhotels in the franchise, such as a global media database, corporatecontact information, information databases, payment services and thelike. In addition, a certain local hotel may desire to have a local SNETinfrastructure 1003 that provides access to local entertainment, dining,news information, device access specific to the local hotel, etc. Thehotel may desire to combine the hotel chain's capabilities provided bythe global SNET infrastructure 1001 with the location-specificcapabilities provided by the local SNET infrastructure into a combinedSNET group 1037, to enable a hotel guest to access global and localcapabilities with a single docking process and via a singlerepresentative 1005 that provides global and local capabilitiespartially or fully combined.

In some embodiments, combinations of capabilities provided by separate,distributed infrastructures are managed, in part or in full, by one ormore (distributed) processing systems, social devices, members,applications/services, etc., that are associated with one or moreinfrastructures. For example, in the illustrated embodiment, aprocessing system associated with the local SNET infrastructure 1003 maymanage the combination of capabilities from infrastructures 1001 and1003 into SNET group 1037, manage docking of client SNET groups 1035with the SNET group 1037, or combinations thereof.

In some embodiments, access to a SNET group 1037 by a client SNET group1035 can be granted, restricted and/or terminated by a network manager,processing system, social device, or some combination thereof accordingto an input, a trigger event, some other internal logic, etc. Forexample, when a social device docked with a client social device/serviceof SNET group 1035 leaves a premises associated with a SNET group 1037,the client SNET group's 1035 access to capabilities provided by SNETgroup 1037 may be terminated by terminating or restricting accessgranted via docking, changing authorization to interact with some or allcapabilities provided by SNET group 1037, undocking the client socialdevice 1035 from SNET group 1037, etc. This can occur automatically orin response to a trigger event, including, without limitation, elapse ofa predetermined time after entering or leaving the premises, or thelike. In some embodiments, a client SNET group 1035 can maintainresidual access to SNET group 1037 after a device docked to the clientSNET group 1035 leaves the premises. For example, where the premisesassociated with SNET group 1037 is a hotel, and a member associated withclient SNET group 1035 belongs to an exclusive hotel membership, theclient SNET group 1035 associated with the member may, after a dockeddevice leaves the premises, still receive at least some access tocapabilities provided by SNET group 1037, including, without limitation,payment services or a call routing phone service.

In some embodiments, a SNET group associated with a member (e.g., ahuman, a device or a service), can be docked to another SNET group toenable the member to access or receive services, contact information,other information associated with the SNET group, exchange information,etc. Such a member can be an existing member of a SNET, a nonmember(also referred to herein as a third party), an authorized guest or thelike. For example, a human user with a device may approach within athreshold, such as a proximity threshold, of an access point for apremises, upon which the access point, or some other device associatedwith the premises delivers an invitation to the device/service or humanuser via the device, to dock to an SNGET group associated with thepremises. The invitation can vary depending upon whether one or both thehuman user and the service/device are already members of the SNET. Forexample, where the device is not a social device, the access point candeliver an invitation in the form of a web page to the device, via abrowser application or the like, that offers the device or device userthe option of joining a SNET group as an ad hoc member. Where the deviceis a social device, the invitation can include a direct invitation todock a SNET group with the premises-associated SNET group via a socialinterface or user interface located within the device.

The invitation can be accepted via one of various acceptance processes.For example, where a social device receives an invitation that includesa unique identifier indicating the SNET group to which the member isinvited to dock, the social device can interact with an access point,another device, a SNET, SNET group, SNET sub-group, and the like via anindependent pathway to accept the invitation. Acceptance in the aboveexample may include simply delivering the unique identifier andinformation identifying the SNET group associated with delivery of theunique identifier, following which the SNET group is docked to thepremises-associated SNET group. In addition, where a non-social deviceattempts to access an access point, and the access point pushes a webpage to a browser application on the non-social device, the acceptanceprocess can include accessing the web page, indicating a desire to dockwith the SNET group (and perhaps providing other information). Inresponse, the non-social device or an affiliated ad hoc guest SNET groupis accepted and docked to the premises-associated SNET group.

Upon accepting an invitation, a human user, service/device or somecombination thereof can gain at least partial access to capabilitiesprovided by a premises-associated SNET group. For example, where thepremises is a coffee shop, a member whose personal SNET group is dockedto a premises-associated SNET group may gain access, via one or moredevices docked to his personal SNET group, to various servicesincluding, without limitation, online newspapers, videos, a menu foritem sales, shopping options for home delivery, ordering interface andpayment services for on-site delivery, etc. In another example, wherethe premises is a hotel or private residence, a member whose personalSNET group is docked to a premises-based SNET group may gain access, viaone or more devices docked to his personal SNET group, to services andinformation, without limitation, access to locally or remotely-storedcontent items, contact information, access to control functionalelements of on-site (robotic) devices, etc. In another example, wherethe premises is a shopping mall, an access point may deliver, push, orthe like an invitation to a device or user of the device to dock to aSNET group associated with the mall. The access point may require thatthe device or user attempt to access the access point before theinvitation is delivered in the form of a unique identifier or web page.Services associated with the SNET group can include, without limitation,advertising, sales and coupon information provided by computing devicesof retail locations within the mall, a mall mapping service that showthose docked to the SNET group the locations of particular stores, amall music service that provides those docked to the SNET group withmusic or other media content served by media sources associated with theSNET group, telephone directory services, a search engine relating toanything within any store in the mall, etc.

In some embodiments, an access point supports delivery of invitations todock to a SNET group, processing acceptances of invitations, and routingof communications between members, ad hoc members, and potential membersof a SNET/SNET group. An invitation may be triggered by an attempt toassociate with the access point. In other embodiments, the access pointautomatically provides the invitation to any device that the accesspoint determines has crossed a threshold, such as a predeterminedproximity threshold or location. Those docked to the SNET group,including ad hoc members, SNET groups, ad hoc SNET groups, and/orcombinations thereof, may be able to couple with other devices/servicesthat are also docked with the SNET group. Upon crossing another (or thesame) threshold, docking to the SNET group can be terminated orrestricted. For example, where a device that enters a premises isoffered an ad hoc docking to a SNET group by an access point, the accesspoint may restrict or terminate the ad hoc docking upon determining thatthe device has left the premises.

FIG. 11 illustrates a schematic block diagram of social networkinggrouping hierarchies according to various embodiments of the disclosure,including interactions between various SNET system, infrastructures,groups, services, and devices. In the illustrated embodiment, a SNETinfrastructure 1102 can include one or more various SNET groups andsocial services/devices. For example, infrastructure 1102 can representa SNET infrastructure associated with a SNET, SNET group, distributedprocessing system, SNET account, SNET member, human, device, and/orsocial service.

In some embodiments, various SNET groups are created by a SNETinfrastructure based upon on an input from a user, member, processingsystem, device/service, SNET, SNET group, etc. For example, where SNETinfrastructure 1102 is associated with a SNET member account, a memberof the account may provide input to the SNET infrastructure 1102 tocreate SNET group 1104. The input can include, without limitation,attributes of the group 1104, social devices/services to be docked withthe group 1104, information to be accessible to one or more members ofgroup 1104, etc.

In some embodiments, a SNET group in a SNET infrastructure is dockedwith another SNET group. For example, in the illustrated embodiment,SNET group 1104 is docked with SNET group 1112 and SNET group 1114 viadocking links 1107 and 1109, respectively. Docking one SNET group toanother SNET group can be accomplished via one or more various dockingprocesses including, without limitation, sole initiation of docking byone or more devices or SNET groups.

In some embodiments, a docking process can include interactions betweenat least portions of both a first SNET group and a second SNET group.For example, where SNET group 1112 is to be docked to SNET group 1104via docking link 1107, SNET group 1112 and SNET group 1104 may exchangesecurity information processing and the like for one or more members,docked devices, functional elements, accessible information, etc. Suchexchanges can enable additional security verifications of appropriateinteractions and access between the two SNET groups and their respectivemembers. In some embodiments, additional security processes, such ashuman confirmation requirements, are employed to ensure secure access tocapabilities of one or more docked SNET groups and/or resources.

In some embodiments, a docking process can include various actionsperformed by one or more of a SNET, SNET system, SNET infrastructure,processing system, SNET group, social device, user, member, or somecombination thereof. Such actions may include, without limitation,verifying an optimal docking location or arranging a presentation ofdocking links to a prospective member. For example, a user associatedwith SNET infrastructure 1102 may interact with the infrastructure todock SNET group 1120 to some part of SNET infrastructure 1124. Thedocking process can include, without limitation, determining an optimaldocking configuration between SNET group 1120 and one or more variousSNET groups in SNET infrastructure 1124 to enable access by a member ofSNET group 1120 to certain services and capabilities of SNETinfrastructure 1124.

As shown in the illustrated embodiment, SNET group 1120 can be dockedwith both SNET group 1132 (via docking link 1146) and SNET group 1134(via docking link 1144) as part of a single docking process to associateSNET group 1120 with certain capabilities provided by various SNETgroups in SNET infrastructure 1124, where the optimum dockingconfiguration is determined to include docking SNET group to both SNETgroup 1132 and SNET group 1134 to access such capabilities. The dockinglinks 1146 and 1144 can be governed by a single docking specification1142, or some other combination of docking specifications that are partof SNET infrastructure 1124. In some embodiments, docking links anddocking specifications can be docked or otherwise associated inone-to-one type relationships, one-to-many type relationships,many-to-one type relationships, etc.

In some embodiments, a docking process that associates SNET group 1120with certain capabilities of SNET infrastructure 1124 via docking withboth SNET group 1132 and SNET group 1134 may include arranging apresentation of the docking links such that a member accessing thecapabilities does not see a full view of the complexity of the dockinglinks and interactions between various SNET groups, devices/services,and SNET infrastructures. In the illustrated embodiment, for example, adocking process for docking SNET group 1120 with SNET groups 1132 and1134 may include arranging a presentation or representative view of thecapabilities of SNET group 1120 that hides the fact that SNET group 1120is being docked, via two docking links, to two SNET groups. A simplifiedpresentation or representative view may present only a view of SNETgroup 1120 being docked with certain capabilities of SNET infrastructure1124. In some embodiments, a member may adjust, toggle, or otherwisemanipulate the complexity of the presentation or representative viewsuch that a partial or full view of the complexity of the docking linksand interactions between the SNET infrastructures, SNET groups, andsocial devices (or services) is presented to a member.

In some embodiments, establishing multiple docking links can provideadditional security for access to certain capabilities. For example,where a docking link 1146 between SNET group 1120 and SNET group 1132includes a high security link to a certain capability than may beprovided for by a second route (e.g., via SNET group 1144 throughdocking links 1144 and 1137), the docking process may includereplicating security requirements across alternate routes. In someembodiments, establishing multiple docking links can provide moreefficient access than a single docking link to capabilities andservices. For example, where a docking process includes a determinationthat a docking link to both SNET group 1132 and SNET group 1134 canenable a more efficient access to certain capabilities of SNETinfrastructure 1124 than a single docking link, a docking process caninclude establishing multiple docking links 1146 and 1144 to SNET groupsof SNET infrastructure 1124.

In some embodiments, a docking link between various SNET groups andsocial devices/services is managed based on various dockingspecifications. A docking specification can, in some embodiments, manageone or more particular docking links and set forth, for example and notby way of limitation, access limitations, restrictions, and grantsassociated with various capabilities of a SNET group, security accessrequirements, periods of access, trigger events upon which access is tobe altered, restricted, granted, and/or terminated.

For example, as shown in the illustrated embodiment, SNET group 1104includes docking specifications 1106 and 1108. Docking specification1106 can, in some embodiments, govern the docking link 1107 between SNETgroup 1104 and SNET group 1112. Likewise, docking specification 1108can, in some embodiments, govern the docking link 1109 between SNETgroup 1104 and SNET group 1114. A docking specification can bepredetermined, in part or in full, by a member of SNET group 1104 inadvance of a docking, created on the fly as part of a docking process todock SNET group 1104 to another SNET group, provided by the SNETinfrastructure or a SNET group that attempts to dock with SNET group1104, etc. For example, a member of SNET group 1104 may establishdocking specification 1106 that restricts access by members of SNETgroup 1112 to capabilities provided by SNET group 1104 based upon alater trigger event including, without limitation, elapse of a period oftime. In some embodiments, a docking specification is specific tocertain attributes of other SNET groups and devices, such that the SNETgroup 1104 is docked to various SNET groups with correlating attributes.For example, Docking specification 1106 may dictate that SNET group 1104is to be docked, via docking link 1107, to a SNET group 1112 that isassociated with a geographic location that is within a predeterminedproximity threshold to a geographic location associated with SNET group1104, and that the docking link 1107 is to be restricted or terminatedif the geographic location associated with SNET group 1112 exceeds theproximity threshold.

In some embodiments, some or all of a docking specification can bedynamically adjusted, managed, altered, created, or deleted based uponan input from a user, member, or other node in a SNETgroup/infrastructure. For example, a member of SNET group 1104 mayestablish docking specification 1106 to govern docking link 1107 withSNET group 1112 to restrict access by a member of SNET group 1112 tocertain capabilities of SNET group 1104, and then interact with SNETgroup 1104, SNET infrastructure 1102, etc., to alter dockingspecification 1106 to provide greater access by a member of SNET group1112 to capabilities provided by SNET group 1104. Such management of adocking specification can be performed at any time in a scheduled or adhoc process with regard to an existing docking link, a dockingspecification governing potential docking links, etc.

In some embodiments, a docking specification governing a docking linkbetween a “higher-tier” SNET group and a “lower-tier” SNET group is partof the higher-tiered SNET group. For example, in the illustratedembodiment, where SNET group 1104 is a higher-tiered SNET group and SNETgroups 1112 and 1114 are lower-tiered SNET groups, the docking links1107 and 1109 between the lower-tiered SNET groups 1112 and 1114 and thehigher-tiered SNET group 1104 are governed by docking specifications1106 and 1108 that are part of the higher-tiered SNET group 1104,thereby enabling control by a higher-tiered SNET group over dockinglinks associated with lower-tiered SNET groups.

In some embodiments, a docking specification can be tailored by a user,member, SNET system, SNET infrastructure, SNET group, or socialdevice/service to provide various levels of interaction and accessbetween various docked SNET groups. For example, in the illustratedembodiment, docking specification 1106 may dictate that docking link1107 provides full bi-directional interactions, sharing of information,services, and the like between SNET groups 1104 and 1112 (via dockinglink 1107). In another example, docking specification 1108 may dictatethat docking link 1109 provides a one-way group-to-group service accessbetween SNET group 1104 and SNET group 1114 via docking link 1109, suchthat a member of SNET group 1114 can access at least some servicesprovided by capabilities of SNET group 1104, but a member of SNET group1104 cannot access some or all information, services, devices, or otherresources associated with SNET group 1114. For example, where a hotelguest's SNET group is docked with a hotel's SNET group to grant thehotel guest access to hotel service capabilities via the hotel's SNETgroup, a docking specification governing the docking link between thehotel guest's SNET group and the hotel's SNET group may specify that thehotel guest is restricted from accessing certain capabilities of thehotel's SNET group, while the hotel's SNET group is restricted fromaccessing any of the capabilities of the hotel guest's SNET groupincluding, without limitation, access to devices docked to the hotelguest's SNET group. As discussed above, such access and interactionaspects of a docking specification can, in some embodiments, be alteredat any time by various users, members, SNET groups, SNETinfrastructures, etc.

In some embodiments, a docking specification places certain restrictionson capabilities of a SNET group that are offered and provided to membersof docked SNET groups. For example, docking specification 1106 maydictate that only certain capabilities of SNET group 1104 are to beprovided to a member of SNET group 1112 via docking link 1107. Dockingspecification 1106 may also dictate that each member of SNET group 1112be provided with a distinct access to a distinct one or morecapabilities of SNET group 1104. For example, docking specification 1106may dictate that each member of SNET group 1112 be provided a uniqueaccess to one or more capabilities of SNET group 1104.

In some embodiments, a docking link between various SNET groups enablesaccess by additional SNET groups to capabilities provided by SNET groupsto which additional SNET groups are indirectly associated or docked. Forexample, in the illustrated embodiments, where SNET group 1104 is dockedto SNET group 1114 via docking link 1109, SNET group 1114 is docked toSNET group 1120 via docking link 1118. Docking link 1118 is governed bydocking specification 1116 in SNET group 1114. In some embodiments, amember of SNET group 1120 may be granted access to at least somecapabilities of SNET group 1104 to which a member of SNET group 1114 isgranted access. Access to capabilities of SNET group 1104 by a member ofSNET group 1120 can be determined by various docking specificationsincluding, without limitation, docking specification 1116 that governsthe docking link 1118 between SNET group 1114 and SNET group 1120, anddocking specification 1108 that governs the docking link 1109 betweenSNET group 1104 and SNET group 1114. For example, docking specification1108 may control access by a member of SNET group 1114 to certaincapabilities of SNET group 1104 via docking link 1109 by restrictingaccess to capabilities of SNET group 1104 by a SNET group that is dockedto SNET group 1114. In another example, docking specification 1116 mayspecify that a member of SNET group 1120 may access none, some, or allof the services and capabilities of other SNET groups including, withoutlimitation, SNET group 1104 to which SNET group 1114 is docked.

In some embodiments, various SNET groups can be docked to each other,such that some or all of the docked SNET groups gain access or some orall of the services and capabilities of the other docked SNET groups. Inthe illustrated embodiment, for example, SNET infrastructure 1124includes SNET group 1126, which is docked, via docking link 1129governed by docking specification 1128, to SNET group 1132 and is alsodocked, via docking link 1131 governed by docking specification 1130, toSNET group 1134. In addition, SNET group 1134 is docked, via dockinglink 1137 governed by docking specification 1136, to SNET group 1132; asa result, SNET groups 1126, 1132, and 1134 are each docked to eachother. The docking links between the SNET groups 1126, 1132, and 1134can provide various levels of access including, without limitation,various levels of security. In addition, in some embodiments, docking toone of the SNET groups in SNET infrastructure 1124 can grant access tosome or all of the capabilities of some or all of the SNET groups towhich the one of the SNET groups is docked.

For example, in the illustrated embodiment, SNET group 1104 can bedocked to SNET group 1126 via docking link 1139. Communication flowingthrough the docking link 1139 can be subject to various dockingspecifications depending on the origin and destination of thecommunication flow. For example, for media content originating from theSNET group 1104 via group member devices, or for storage or servicesassociated directly with the SNET group 1104, a docking specification1138 may govern any attempted access (via a docking link 1139) to suchmedia content. Such access can include, without limitation, receipt ofmedia content, delivery of media content, identifying media content,information associated with the media content, payment authorizations,etc.

For example, where a foreign SNET group, including, without limitation,a SNET group associated with a separate SNET infrastructure, docks to aSNET group 1104 that includes a first, second, and third media contentoriginating from group member devices, storage and/or servicesassociated directly with the SNET group 1104, the docking specification1138 may specify that: 1) the existence of the first media content isnot to be identified to the foreign SNET group, 2) the second mediacontent can be identified to at least the foreign SNET group as existingbut requires a high level of DRM and is offered at a reduced quality,and/or 3) the third media can be identified to at least the foreign SNETgroup as existing and is offered in its original form withoutredistribution and consumption restrictions. Likewise, dockingspecification limitations placed on data or media content originatingfrom the SNET group 1114 may permit chained access by the SNET group(s)1126, 1132, 1134 (or some combination thereof) via one or more of SNETgroup 1104, SNET group 1120, etc.

In addition to docking specification limitations applicable to localgroup offerings, various docking specification limitations may alsoapply to chained offerings. For example, the SNET group 1114 may freelyprovide access by any other SNET group, via a direct docking link toSNET group 1114, or via an indirect link via a docking link to a SNETgroup that is docked to SNET group 1114, to all offerings including,without limitation, services, content, data, access to docked devices,etc. Such freely-provided access can be defined, in some embodiments,via the docking specification 1116. However, the docking specification1138 may place restrictions on access via SNET group 1104 including,without limitation, not permitting any access or knowledge of some orall offerings from any external SNET group to which SNET group 1104 isdocked including, without limitation, SNET groups 1114, 1112, and 1120.In this manner, and depending on the docking linkage and chained SNETgroups and device specifications, offerings may be managed in variousways depending on underlying needs.

In some embodiments, such linkages and chain management of overallofferings apply twice: one for each direction of access. For example,offering restrictions associated with the SNET infrastructure 1102 canbe completely different from those of the SNET infrastructure 1124. Inaddition, even though all relevant docking specifications within theSNET infrastructure 1102 may permit at least limited access to aparticular offering to the SNET Group 1126, such access may not extendto, for example, the SNET group 1132 due to: the docking specification1128 placing further access restrictions beyond those required by theSNET infrastructure 1102, a relevant docking specification within theSNET infrastructure 1102 that limits foreign linkages, etc.

For example, in an ad hoc travel network docking configuration, apersonal SNET group construct of a traveler (e.g., the SNETinfrastructure 1102) might desire to provide very limited access to ahotel's SNET group construct (e.g., the SNET infrastructure 1124), whilein the other direction the hotel's SNET group construct offerings may befreely provided. Each construct need only provide access to whateverofferings, membership identification, information, and the like thatthey would like to expose. A traveler may choose to expose, for example:a payment service element located somewhere within the overall personalSNET group construct; the traveler's social smartphone's incomingmessage service; an administrator's incoming message service; and/or atravel document storage service. The hotel may choose to exposecapabilities, offerings, and the like including, without limitation: aregional directory, a map and other information services, a conciergeservice, a billing service, a reservation service, networked officeequipment, etc. Exposure in either case can be defined, for example, viavarious docking specifications associated with the originating SNETgroup as modified by the docking specifications associated with the SNETgroups in the chained pathway to the destination.

In some embodiments, docking specifications can be extended to provideresolution beyond that of a group level. For example, the dockingspecification 1128 governing docking link 1129 may require humanauthentication and various levels of security before providing accessvia docking link 1129. In another example, as defined by the dockingspecification 1128, a traveler (e.g., a member of the SNET group 1104)may gain access to a particular offering provided by one element,service or device participant in the SNET Group 1126 via a requiredsecure interaction with the traveler's local social smart phone asdocked to SNET group 1104. However, some or all other members of SNETgroup 1104 or other SNET groups may not gain access to the particularoffering. In other words, for one or more particular SNET groupofferings, capabilities, offering identifiers etc., and for one or moreparticular group members, chained docking specification details can beestablished to manage overall access, including, without limitation,limited access. Although shown functionally as being distributed,docking specification flow can be managed by a single user interface,and may be stored in a single database construct.

In some embodiments, default docking specifications can apply a defaulttreatment for access, offerings, interactions, etc. with regard to oneor more particular SNET groups, but permit specific offering/accessmodifications where needed by authorized SNET nodes and/or groups.Likewise, overall default treatment can be modified.

In some embodiments, a docking specification can be part of one or moreSNET groups, SNET infrastructures, social device, etc. For example,where a docking process to dock SNET group 1104 to SNET group 1126 isinitiated by a device docked to SNET group 1104, docking specification1138 may be a part of SNET group 1104. In addition, where a dockingprocess to dock SNET group 1104 to SNET group 1126 includes some part ofSNET infrastructure 1124 receiving and granting a docking request fromsome part of SNET infrastructure 1102, docking specification 1138 may bea part of SNET group 1126. In some embodiments, a docking request caninclude, without limitation, a request to dock one SNET group to anotherSNET group, a request to provide a first SNET group's capabilities,including without limitation services and device resources, to one ormore devices docked to a second SNET group. A docking request canoriginate from a device docked to the first SNET group, a device dockedto the second SNET group, a member of the first SNET group, a member ofthe first SNET group, a third-party, or some combination thereof.

By docking to SNET group 1126, SNET group 1104 may access some or all ofthe capabilities of SNET group 1132 and SNET group 1134, as specified byone or more of docking specifications 1138, 1128, and 1130. Conversely,where SNET group 1104 docks with SNET group 1134, SNET group 1104 mayaccess some or all of the capabilities of SNET group 1126 and SNET group1134, as specified by one or more of docking specifications 1138 and1136.

In some embodiments, docking various SNET groups with other SNET groupscan include access restrictions and limitations. For example, where SNETgroup 1104 is docked to SNET group 1114, which is docked to SNET group1120 (all within SNET infrastructure 1102), various levels ofinteraction and access by the various SNET groups can be determined viamanagement of the various docking specifications 1108 and 1116 governingthe docking links. All three docked SNET groups 1104, 1114, and 1120 canbe enabled to have access to some or all of each other's capabilities,SNE group 1114 may have access to capabilities of SNET group 1104 whileSNET group has access to capabilities of SNET group 1114, SNET groups1104 and 1114 may have access to each other's capabilities while SNETgroup 1120 has access to some of the capabilities of SNET group 1104 andsome of the capabilities of SNET group 1114. Such interactions, accessand dockings may be performed without any interaction with a third-partyentity or third-party SNET group.

In some embodiments, where a third-party entity or third-party SNETgroup is involved in a docking link, additional interaction with suchthird-party may be required. For example, where SNET group 1104 is to bedocked to SNET group 1126, and the respective SNET groups are part ofseparate SNET infrastructures, docking, access, or the like may requireinteraction with a third-party. Interaction may include, by way ofexample, a security challenge, invitation and/or acceptance to a memberof SNET group 1104 that is attempting to access services or othercapabilities of SNET group 1126. In some embodiments, a docking processbetween SNET groups associated with separate SNET infrastructures can beinitiated, managed, or the like by various nodes of a SNETinfrastructure. For example, a docking between SNET group 1104 and SNETgroup 1126 may be managed by one or more devices docked to SNET group1104, one or more devices docked to SNET group 1126, one or more devicesdocked to a third-party SNET group, one or more processing systems, oneor more SNET infrastructures, etc.

In some embodiments, a SNET “travel” group facilitates and/or monitorstravel activities, activities associated with an aspect of a socialdevice, an aspect of the social device, and/or a SNET group associatedwith a member. An activity can include one or more events includingtrigger events, the occurrence of which can influence at least oneaspect of the SNET group. The SNET travel group can be docked to SNETgroups comprising entities relevant to one or more activities, travelcompanions, family members, friends and people to be visited,restaurants, coupon/rebate services, etc. A member of a SNET travelgroup (which can be temporary or persistent) can receive, for example,detailed hotel information (including confirmations, rates, feedback,amenities, restaurant recommendations, nearby attractions, etc.), anattendee list for a social event/excursion, babysitter monitoringservices, etc. In some embodiments, one or more elements associated withthe SNET travel group can be managed by one or more processing systems,server devices, network nodes, remote devices or the like in response toone or more trigger events or inputs from one or more SNET groupmembers/nonmembers.

FIG. 12 is a schematic block diagram illustrating access to socialservices and other resources participating in a social networkgroup/sub-group 1206 in accordance with an embodiment of the presentdisclosure. In this embodiment, a member of a social group controlsdifferent access levels to both personal information (which may beincluded in a user profile) and associated device profiles andcapabilities. Such access rights allow the member to establishselective, restricted and/or tiered access rights and views—for othermembers of the social/group as well as non-members—to all or some of themember's social devices, services and other resources.

In the illustrated embodiment, a member or device of a SNET group 1206(or, alternatively, an unaffiliated entity or node of SNETgroup/sub-group 1213) accesses social group services and resources 1210associated with the SNET group 1206 via a services and resourcemanagement node 1200. The services and resource management node 1200 ofthis embodiment comprises access rights 1201, access views 1202, dynamic(re)allocation functionality 1203, arbitration functionality 1204, andsecurity functionality 1205.

In operation, the access rights 1201 and access views 1202 controldiffering access levels and access visibility for a member's personalinformation, device information, data, services, processing and storagecapabilities, and other social resources. Access rights 1201 and accessviews 1202 can be predefined, for example, based on a SNET group, basedon co-member devices, or based on member's own device to deviceinteractions. Such predefinition can be tailored dynamically as neededor as relationships change. Access rights 1201 may also be expanded tosupport temporary interaction with a guest member or visitor device. Forexample, a visiting member with a smart phone may be permitted toreceive/provide media to a social device residing in a “home circle.”

In some embodiments, a member of the SNET group 1206 can adjust andmodify access rights 1201 on an information-by-information basis,device-by-device basis, member-by-member basis, etc. Through accessviews 1202, the member might also present itself in various waysdepending on context, location, or use-based considerations. Forexample, a member icon/avatar may present differing characteristics orcapabilities that are context dependent, including work, home or socialsettings. Allocation and (as necessary) dynamic reallocation of socialservices/resources is performed by dynamic (re)allocation functionality1203 and arbitration functionality 1204. Access to socialservices/resources can be preconditioned on secure access/authenticationperformed by security functionality 1205.

In addition to social group services and resources 1210, the SNET group1206 might include, for example, a SNET server 1212 and one or morehuman (or AI personas/functions) members 1214 and affiliated socialdevices, services, applications, files, web pages, connections and othersocial resources. As will be appreciated, a human member 1214 canestablish selective or tiered access to personal information andassociated social device profiles and other resources as describedabove. In certain embodiments, the services and resource management node1200 may be incorporated in system circuitry of an SNET (proxy) server1212 or other SNET social device, or administered by a SNET hostinginfrastructure, either in a standalone or distributed manner. Further,the SNET server 1212 may include a firewall operable to provide secureaccess and perform basic routing functions.

Access to social group services and resources 1210 by nodes of the SNETgroup/sub-group 1213 may occur in a variety of ways, including via auser interface (UI) 1218 utilized by one or more humans 1216. The UI1218 might comprise a graphical user interface (GUI) or browser thatgraphically indicates available resources, voice controls, gesturecommands, etc. Access to the SNET group 1206 can also be managed by aproxy server 1220. The proxy server 1220 functions as an intermediaryfor access requests from proxy clients 1222—including social servicesand/or devices connected to the proxy server 1220 via the Internet orother IP-based networks—seeking to communicate with the SNET group 1206.Social devices 1224 affiliated with a SNET group/sub-group 1213 may havethe capacity to interact directly with the SNET group 1206. It is notedthat the human members 1216, proxy server 1214 and social devices 1224may operate independently of a SNET group/sub-group. Further, the proxyserver 1214 may be a distributed or cloud-based entity, or a member of(or incorporated in a member of) either the SNET group/sub-group 1213 orSNET group 1206.

FIG. 13 is a logic diagram of a method for allocating social resourcesand services in accordance with an embodiment of the present disclosure.In an initial step 1300, a SNET member or other SNET node establishes aSNET account that identifies relevant SNET groups, affiliated servicesand/or other social resources. Next, or contemporaneously, in step 1302SNET groups, social devices and/or services are “docked” (e.g., online,through near-field communications (NFC) and/or Bluetooth coupling, orvia networked operations) to the SNET account. Such docking may involvesecurity and authentication operations 1304 and other operations such asthose described elsewhere herein.

The method continues in step 1306 with the creation of one or morecircles or (sub)groups (e.g., a distributed SNET group) including aselection of available services and resources (e.g., billing services orAI functions) that may have related or specific characteristics andinterdependencies, etc. In one embodiment, members may be added to agroup through a drag-and-drop user interface or other means. In step1308, access tiers and views are manually or automatically defined forselect information, services, and other affiliated social resources.This step may be conducted in whole or part by means of a (pop-up) tableor form that requests tier settings and allows for personal tailoring ofsame. The member may select a particular group member (device/service orhuman/self) to reveal tier characteristics and allow modification ofaccess rights. In some circumstances, selection of access rights may bebased on profile data and other characteristics of a particular device,user or group seeking access to social resources. Further, distinctaccess rights, including content and capabilities access views, may beassigned to different social device resources or groupings of resources,or to a particular request for access to social resources.

In step 1310, access tier/view characteristics are communicated toauthorized SNET group members, which may include social services ordevices (including the member's social devices), human members, AIfunctions/personas, a SNET and/or one or more SNET groups. Next, in step1312, social services and resources are allocated in accordance with theaccess tiers and views communicated in step 1310. Allocation of a socialresource/service may entail, for example, allocating the resource fordedicated use by a member of the SNET group, either on a persistent ortemporary basis, subject to reallocation. Subsequent reallocation mayoccur, for example, if access to a previously allocated social resourceis requested by a second member (or non-member) having a higher priorityor superior access rights to the resource. In certain embodiments of theinvention, social resources may be dynamically offered and allocatedif/when and to the extent such resources become available. Management ofsocial resource reserves, including termination of related services, maybe performed by individual devices, groupings of devices, and/orcentralized or distributed SNET processing circuitry and software.

FIG. 14 is a logic diagram of a method for establishing tiered views ofand access to social resources and services in accordance with anembodiment of the present disclosure. First, the availability of asocial resource/service for access by SNET groups or members isdetermined in step 1402. Next, access rights and access views for thesocial resource/service are established in step 1404. Such access rightsand views may provide for levels of access having varying degrees ofgranularity as contextually appropriate and as determined by one or moreSNET nodes having control of the social resource/service, or asdetermined by an authorized entity requesting access to the socialresource/service.

Established levels of access rights are then applied to permit access toand allocation of the social resource/service in step 1406. Ifconflicting, modified or additional requests for access are identifiedin step 1408, reallocation and/or arbitration is performed in step 1410as necessary to address conflicts or otherwise service such requests. Inone embodiment wherein a particular device or user requires or requestsa relatively large percentage of available resources/services, accessmay be denied or restricted, including on a temporary or persistentbasis. Alternatively, other capable and available socialresources/service may be employed to resolve such requests. Potentialoveruse or abusive use of a SNET resource may be detected by SNETmonitoring functionality that employs static or dynamic thresholds.

Referring now to FIG. 15, a logic diagram is shown for a method forarbitrated access to social resources/robotics in accordance with anembodiment of the present disclosure. Upon activating or docking asocial device resource/robotics, account information is automatically(or via a setup prompt) provided to the SNET group. Next, in step 1502,operational control of the social device resource/robotics is conferredto a node or distributed process of the SNET group. This node or processthen generates contextually appropriate control signals etc. as shown instep 1504. Such control signals and contextually-related applicationsare communicated to the social device resource/robotics, possibly via astandardized communication protocol.

In response to the control signals, the social device resource/roboticsperforms one or more functions, either automatically or as authorized bya user, in step 1506. Further interaction and data exchange with thesocial device resource/robotics may occur in step 1508 including, forexample, artificial intelligence/neural network training operations,control function customization, software maintenance, load balancing,etc. In subsequent step 1510, control of the social deviceresource/robotics is terminated or relinquished to a user or other SNETnode.

In certain embodiments, some social device resources/robotics maysupport only one member interaction at a time, with or withoutsimultaneously supporting the underlying owner/member. Other devices maysupport many multiple members (devices/AI/humans) as well as havingdedicated functionality reserved for an owner. A standardized ormanufacturer proprietary approach to control and certification markingmay account for such variations in SNET device capabilities. Monitoring,snooping of content (e.g., for purposes of protecting copyright owners)and like functionality could also be accomplished through compliancewith such a standardized protocol.

In a further embodiment of a SNET/SNET group according to the inventionis illustrated, an authorized guest member may control remote roboticsand/or the social devices of another via one of the guest's own socialdevices, or vice versa. Such control can be established in advance (atthe factory) or managed in real time via guest interaction. Utilizationof certain control features, such as features allowing content to bedriven and played on another's device, may be restricted, for example,to members or friends of a particular SNET group that allows content orprocess snooping.

By way of illustration, a social camera might capture and store homevideo, post a link thereto via a family SNET, and then enter a lowpower/sleep mode. A family circle member residing in another country,for example, could then activate an associated social television thatparticipates in the family circle. Next, a channel entry for the postedmedia may become visible and trigger video playback. In turn, a commandis triggered to wake up and stream video content to the socialtelevision.

As will be appreciated, authorized control of another's social deviceenables a variety of other applications. By way of example, a deviceuser joins a church social circle and docks one or more of her socialcommunication devices (e.g., a smart phone). In conjunction therewith,the church docks a social control application interface or socialapplication (managed, for example, by a priest/pastor) into the circle.Thereafter, via automatic in-range determinations (GPS tracking,WiFi/NFC presence, etc.), the social control application/interfacedelivers context appropriate control signals to the user's socialdevice(s). Other control signals may be provided to automaticallycollect donations or automatically deliver a prompt for same,automatically deliver a hymnal, provide a worship service agenda, etc.For example, the user phone may be instructed to enter into emergencyonly and do-not-disturb (e.g., vibrate only) modes of operation.Similarly, social automated device control may be used to configure,program or collect status information for appliance devices, (e.g., awashing machine or thermostat). A user may designate controljurisdiction and/or data collection capabilities to a friend, circlemember(s) or application interface/application.

FIG. 16 is a schematic block diagram illustrating remote access tosocial resources of a social network circle/sub-circle in accordancewith and embodiment of the present disclosure. In the illustratedembodiment, a social device 1600 may indicate a desire to associate,dock, access social device resources and other circle resources 1618, orotherwise communicate with a (secure) SNET circle/sub-circle 1602. Thesocial device 1600 device can be autonomous and independent or,alternatively, a participant in a second SNET circle 1604 or othernetwork serviced by the SNET gateway 1606.

In one embodiment, either the SNET gateway 1606 or SNET circle gateway1608 functions as a proxy for the social device 1600. Proxyfunctionality within the SNET gateway 1606 may be provided by a softwareapplication or a computer system (server) that functions as anintermediary for requests from clients (including connected socialdevices) seeking resources from other servers or gateways such as SNETgateway 1608. Such resources might include files, services, web pages,connections, profiling information and other available social deviceresources and other circle resources 1618.

The SNET gateway 1606 may evaluate requests from social devicesaccording to various filtering rules. For example, the SNET gateway 1606might filter traffic by IP address or protocol. Once a request from thesocial device 1600 validated (if necessary), the SNET gateway 1606connects to the SNET circle gateway 1608 over a WLAN/LAN or othercommunication path and requests access to resources of the SNETcircle/sub-circle 1602 on behalf of the social device 1600.

Membership in the SNET circle/sub-circle 1602 is established through adocking module 1610 of SNET processing circuitry and software 1612,which may support one or more device discovery and configurationprotocols, including standardized protocols. When circle membership isrestricted, a local or cloud-based registrar 1614 can be employed toprovide authentication. The registrar 1614 of the illustrated embodimentmay utilize an administrator, or a directory service 1616 such as aLightweight Directory Access Protocol (LDAP)-based directory server thatstores attribute data. LDAP is a well-known application protocol forquerying and modifying items in directory service. When docking with anIP-based SNET circle, a social device may broadcast profile data to thelocal domain using a textual data format such as Extensible MarkupLanguage (XML). In one exemplary docking process, a social devicebroadcasts a request to register with or access a SNET circle/group. Therequest may occur as part of initiation or power-up of the socialdevice, on a proximity or ad hoc basis, or following another triggerevent. The registration request may be received by at least one gatewaydevice. The gateway functions to configure the social device such thatit can communicate with other hosts. In an IP-based network, typicalconfiguration information might include an IP address and default routeand routing prefix. The gateway may be a standalone device,multi-function computing device, etc., and can operate in an ad hocmanner or be persistent.

In one illustrative embodiment, the network configuration protocolutilized by the gateway may be the Dynamic Host Configuration Protocol(DHCP) and related standards, promulgated and maintained by the InternetEngineering Task Force (IETF), or similar protocol that automatesnetwork-parameter assignment to network aware social devices/services.In addition to eliminating the need for manual device configuration,DHCP provides a central database of devices that are connected to thenetwork and eliminates duplicate resource assignments.

Upon a trigger event (e.g., power-up, registration with a SNET circle,etc.), the social device can transmit configuration/capabilityinformation to one or more other devices. Such information may beadvertised to specific devices identified by the social device. Theconfiguration/capability information may also be transmitted to anydevice in a SNET circle, or any device capable of receiving thetransmission. A device can, in some embodiments, determine theconfiguration/capability information of other devices by querying them,individually or as a group.

SNET circle resources may also be accessible via a zero configuration,multi-cast discovery protocol that locates devices, such as printers,and the services offered by those devices on a local network using amulticast discovery protocol and related service records or profilinginformation. Such a protocol may operate at the application layer, andtransmissions of configuration/capability information can be used, forexample, to identify and utilize common programming interfaces,protocols, packet formats, and the like between two or more devices. Inaddition, a bridge or proxy node that communicatively couples two ormore devices may utilize a multicast-type discovery and access protocol.In certain embodiments, a bridge or proxy node may communicate or relayqueries and advertisements regarding configuration/capabilityinformation, and may further operate to process, transcode or modifytransmissions relating to configuration/capability information ofdevices.

Wide area service discovery of SNET circle resources may be enabledthrough an appropriately configured domain name service (DNS) server orthe like, or a multicast-type protocol that performs DNS-likeoperations. Further, SNET circle resources may be configured to supportinteroperability guidelines and network protocols, such as UniversalPlug and Play (UPnP), that provide uniform mechanisms and restrictionsfor accessing resources and data over a network.

Depending on the particular implementation, gateway (DHCP server) mayutilize various methods to assign and allocate IP addresses. Briefly, anetwork/SNET circle administrator can assign a range of available IPaddresses. Each social device can be configured to request an IP addresswhen joining a SNET circle or during SNET circle initialization. Next,an IP address can be granted using a “lease” approach that includes aconfigurable time period, thereby enabling the gateway to dynamicallyreclaim and then reallocate IP addresses that are not renewed (e.g., asocial device powers off or otherwise terminates communication with aSNET circle).

Alternatively, the DHCP server may permanently assign an available IPaddress to a social device. Under this approach (and the “lease”approach), the DHCP server maintains a table of previous IP addressassignments, such that it may preferentially assign an IP address thatwas previously assigned to a requesting social device. In yet anotherapproach, a DHCP server may restrict IP address assignment to devicesincluded in a table with MAC address and IP address pairs.

Once the social device is configured, the gateway communicates with afirewall to open up communication ports, thereby permitting networktransmissions to/from the social device. Registered ports are typicallyused by networked applications as transitory source ports whencontacting servers, but they can also identify named services that havebeen registered by a third party.

In addition to opening ports for devices, the firewall may function toadvertise the social device to local and remote users/devices andservices over, for example, a WAN/(W)LAN communication channel. In oneembodiment, social device IP addresses and profiles are communicated toSNET circle members and remote users/devices. In another embodiment, agateway may function as a proxy (such as described above) for socialdevices, including legacy devices that might otherwise require humaninvolvement. The firewall may be software-based (e.g., as part of anoperating system), or comprise various combinations of software,firmware and/or hardware components. In addition, the gateway mayinclude bifurcated firewall functionality for connections to SNETcircles/sub-circles and remote devices, respectively.

When SNET circle membership is restricted, a local or cloud-basedregistrar can be employed to provide authentication services (using adirectory service, for example). The registrar may be located in or oneither side of the gateway, including after firewall, or it may operateindependently of a gateway. Further, the registrar might provideregistration functions for both the social device and/or a remoteruser/device.

When docking with an IP-based SNET circle, the social device 1002 maybroadcast profile data to the local domain using a textual data formatsuch as Extensible Markup Language (XML). Upon successful docking of anew social device, a SNET circle node (e.g., docking module) providesauthorized access to SNET circle. It is contemplated that the socialdevice may simultaneously participate in more than one SNET circle.

As noted, SNET circle resources and social devices may be accessible viaa zero configuration, multicast discovery protocol that locates devicesand the services offered by those devices on a local network using arelated service records or profiling information. Such a protocol mayoperate at the application layer. Wide area service discovery of SNETcircle resources configured in this manner may be enabled through anappropriately configured domain name service (DNS) server.

SNET circle communications in accordance with the disclosure may utilizea variety of transmission protocols. By way of example, mostcommunication over the Internet is currently performed in accordancewith the Transmission Control Protocol (TCP) and User Datagram Protocol(UDP). As is known, TCP typically provides an intermediate level ofcommunication services between, for example, an application program andthe Internet Protocol (IP). Port numbers are used to identify end-pointsfor sending and receiving applications on a host (often referred to as“Internet sockets” or “network sockets”). Internet sockets facilitatedelivery of incoming data packets to an appropriate application processor thread, as determined by a combination of local and remote (e.g.,SNET circle) IP addresses and port numbers. In some embodiments, theReal-time Transport Protocol (RTP) running over UDP may be employed forvideo streaming applications, real-time multiplayer gaming, voice overIP (VoIP), and like applications that are tolerant of a certain level ofpacket loss and may not require a dedicated end-to-end-connection.

A member of a SNET in accordance with various embodiments of thedisclosure such as those disclosed herein may establish permissionsand/or privacy settings that control and restrict who or what may accessthe member's profile(s) information, connections and circles, as well asdefine desired degrees of access. Permissions may enable the user tomaintain certain information as private or available on a permissivebasis only. For example, visibility of specified user information may belimited to users/devices in a SNET(s). Alternatively, specified userinformation may be publicly available. Likewise, a SNET member mayselectively decide to permit others to access personal information suchas name, gender, contact information/email address, etc.

FIG. 17 is a schematic block diagram of an embodiment of a social devicecomprising integral functionality operable to support social networkcircle/sub-circle membership and communications in accordance with thedisclosure. In the illustrated embodiment, a communication interface andtransceiver circuitry 1702 is operable to perform wired or wirelesscommunications between the social device 1700 and a SNET group/sub-group1726 over one or more communication channels. Depending on thecapabilities and configuration of the social device 1700, communicationswith a SNET may be unilateral or bidirectional/interactive, and utilizeeither a proprietary or standardized communication protocol.Communications may include, for example, device profile information,user and SNET circle profile information, control signals, audio/videocontent, interactions with hosted service data, user data, relayedinformation, etc.

The social device 1700 further includes processing circuitry 1704operable to process and manage communications, services and associationsbetween the device and other entities including members of a SNETgroup/sub-group 1724, third parties, software agents, etc. Moreparticularly, the processing circuitry 1704 may include, for example, asoftware management application 1712 comprising one or more of dockinglogic 1714 (including support for device discovery and configurationprotocols such as described below), communication protocol control 1716,service and resource management 1718, and security/authentication 1720functionality.

The social device 1700 further may utilize that may take many forms andbe maintained in static or dynamic memory 1724. Such profile informationenables a social device and/or user to present an image of itself andits capabilities to other members of a SNET. In particular, device/groupprofile information and other resources 1706 and user profileinformation 1708 may be utilized in various ways in accordance with thedisclosure to facilitate a variety of social interactions. Depending onthe capabilities and requirements of a particular device (and othermembers of a SNET), a device or user profile may be static or dynamic.

In certain embodiments, the social device 1700 may interact with auser(s) via user interface circuitry 1710. User input to the socialdevice 1700 may include, for example, data entry through a keypad,touchscreen, remote control device, gaming controller, device controlbuttons, voice or gesture commands, storage device, etc. For example,voice or gesture commands may be utilized to trigger intelligentservices. Authorized access to or control of the social device 1700 canbe facilitated through unique biometric identifiers, passwords,token-based identification, trusted authorities or documents such as adriver's license or passport, and like authentication means.

The social device 1700 may perform core or underlying functionality1720, (e.g., a social appliance, security device, vehicularcommunication node, etc.). Alternatively, the social device mayprimarily function as a social networking interface or communicationdevice, or be programmable to perform specific functions within a SNETgroup/sub-group.

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. Such an industry-accepted toleranceranges from less than one percent to fifty percent and corresponds to,but is not limited to, component values, integrated circuit processvariations, temperature variations, rise and fall times, and/or thermalnoise. Such relativity between items ranges from a difference of a fewpercent to magnitude differences. As may also be used herein, theterm(s) “operably coupled to”, “coupled to”, and/or “coupling” includesdirect coupling between items and/or indirect coupling between items viaan intervening item (e.g., an item includes, but is not limited to, acomponent, an element, a circuit, and/or a module) where, for indirectcoupling, the intervening item does not modify the information of asignal but may adjust its current level, voltage level, and/or powerlevel. As may further be used herein, inferred coupling (i.e., where oneelement is coupled to another element by inference) includes direct andindirect coupling between two items in the same manner as “coupled to”.As may even further be used herein, the term “operable to” or “operablycoupled to” indicates that an item includes one or more of powerconnections, input(s), output(s), etc., to perform, when activated, oneor more its corresponding functions and may further include inferredcoupling to one or more other items. As may still further be usedherein, the term “associated with”, includes direct and/or indirectcoupling of separate items and/or one item being embedded within anotheritem. As may be used herein, the term “compares favorably”, indicatesthat a comparison between two or more items, signals, etc., provides adesired relationship. For example, when the desired relationship is thatsignal 1 has a greater magnitude than signal 2, a favorable comparisonmay be achieved when the magnitude of signal 1 is greater than that ofsignal 2 or when the magnitude of signal 2 is less than that of signal1.

As may also be used herein, the terms “processing module”, “processingcircuit”, and/or “processing unit” may be a single processing device ora plurality of processing devices. Such a processing device may be amicroprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on hard coding of the circuitry and/oroperational instructions. The processing module, module, processingcircuit, and/or processing unit may be, or further include, memoryand/or an integrated memory element, which may be a single memorydevice, a plurality of memory devices, and/or embedded circuitry ofanother processing module, module, processing circuit, and/or processingunit. Such a memory device may be a read-only memory, random accessmemory, volatile memory, non-volatile memory, static memory, dynamicmemory, flash memory, cache memory, and/or any device that storesdigital information. Note that if the processing module, module,processing circuit, and/or processing unit includes more than oneprocessing device, the processing devices may be centrally located(e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributed (e.g., cloud computing via indirectcoupling via a local area network and/or a wide area network). Furthernote that if the processing module, module, processing circuit, and/orprocessing unit implements one or more of its functions via a statemachine, analog circuitry, digital circuitry, and/or logic circuitry,the memory and/or memory element storing the corresponding operationalinstructions may be embedded within, or external to, the circuitrycomprising the state machine, analog circuitry, digital circuitry,and/or logic circuitry. Still further note that, the memory element maystore, and the processing module, module, processing circuit, and/orprocessing unit executes, hard coded and/or operational instructionscorresponding to at least some of the steps and/or functions illustratedin one or more of the Figures. Such a memory device or memory elementcan be included in an article of manufacture.

The present invention has been described above with the aid of methodsteps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claimed invention. Further, theboundaries of these functional building blocks have been arbitrarilydefined for convenience of description. Alternate boundaries could bedefined as long as the certain significant functions are appropriatelyperformed. Similarly, flow diagram blocks may also have been arbitrarilydefined herein to illustrate certain significant functionality. To theextent used, the flow diagram block boundaries and sequence could havebeen defined otherwise and still perform the certain significantfunctionality. Such alternate definitions of both functional buildingblocks and flow diagram blocks and sequences are thus within the scopeand spirit of the claimed invention. One of average skill in the artwill also recognize that the functional building blocks, and otherillustrative blocks, modules and components herein, can be implementedas illustrated or by discrete components, application specificintegrated circuits, processors executing appropriate software and thelike or any combination thereof.

The present invention may have also been described, at least in part, interms of one or more embodiments. An embodiment of the present inventionis used herein to illustrate the present invention, an aspect thereof, afeature thereof, a concept thereof, and/or an example thereof. Aphysical embodiment of an apparatus, an article of manufacture, amachine, and/or of a process that embodies the present invention mayinclude one or more of the aspects, features, concepts, examples, etc.described with reference to one or more of the embodiments discussedherein. Further, from figure to figure, the embodiments may incorporatethe same or similarly named functions, steps, modules, etc. that may usethe same or different reference numbers and, as such, the functions,steps, modules, etc. may be the same or similar functions, steps,modules, etc. or different ones.

Unless specifically stated to the contra, signals to, from, and/orbetween elements in a figure of any of the figures presented herein maybe analog or digital, continuous time or discrete time, and single-endedor differential. For instance, if a signal path is shown as asingle-ended path, it also represents a differential signal path.Similarly, if a signal path is shown as a differential path, it alsorepresents a single-ended signal path. While one or more particulararchitectures are described herein, other architectures can likewise beimplemented that use one or more data buses not expressly shown, directconnectivity between elements, and/or indirect coupling between otherelements as recognized by one of average skill in the art.

The term “module” is used in the description of the various embodimentsof the present invention. A module includes a processing module, afunctional block, hardware, and/or software stored on memory forperforming one or more functions as may be described herein. Note that,if the module is implemented via hardware, the hardware may operateindependently and/or in conjunction software and/or firmware. As usedherein, a module may contain one or more sub-modules, each of which maybe one or more modules.

While particular combinations of various functions and features of thepresent invention have been expressly described herein, othercombinations of these features and functions are likewise possible. Thepresent invention is not limited by the particular examples disclosedherein and expressly incorporates these other combinations.

1. (canceled)
 2. A method for allocating resources in a social networkcircle supported by a social network infrastructure having membershipmanagement functionality, the method comprising: detecting, by thesocial network infrastructure, a social device having a social deviceresource capable of being shared with members of the social networkcircle; offering an invitation to the social device to participate inthe social network circle; receiving an acceptance of the invitationfrom the social device; automatically docking the social device with thesocial network circle to establish membership therein, membership of thesocial device within the social network circle separate from membershipof a corresponding user of the social device; establishing access rightsfor the social device resource of the social device; identifying arequest, from a second member of the social network circle, for accessto the social device resource; and in response to the request,permitting access to the social device resource of the social device inaccordance with the access rights.
 3. The method of claim 2, whereindocking of the social device with the social network circle includesestablishing operational control of the social device resource by thesocial network infrastructure.
 4. The method of claim 2, whereinestablishing access rights for the social device resource includesestablishing a plurality of levels of access rights, and whereinpermitting access to the social device resource includes selecting oneof the plurality of levels of access rights.
 5. The method of claim 4,further comprising: determining profile information associated with thesecond member of the social network circle, wherein selecting one of theplurality of levels of access rights is based, at least in part, uponthe profile information.
 6. The method of claim 2, further comprising:identifying a second request for access to the social device resource bya third member of the social network circle or an authorized non-memberof the social network circle; establishing a relative priority betweenthe first and second requests; and responding to the relatively lowerpriority request by permitting constrained access to the socialresource.
 7. The method of claim 6, wherein constrained access to thesocial device resource comprises suspension of access pending resolutionof the higher priority request for access to the social device resource.8. The method of claim 2, the social network hosting infrastructurehaving resource allocation management functionality, wherein permittingaccess to the social device resource is performed by the resourceallocation management functionality.
 9. The method of claim 2, thesocial device resource selected from the group consisting of: socialdevice user profile information; social device configurationinformation; social device status information; social media content; andsocial device data.
 10. The method of claim 2, the social deviceresource selected from the group consisting of: processing capabilities;allocable communication bandwidth; storage resources accessible via thesocial device; services; and attached device resources.
 11. The methodof claim 2, wherein detecting a social device having a social deviceresource capable of being shared with members of the social networkcircle includes determining a location of the social device, and whereinoffering an invitation to the social device to participate in the socialnetwork circle includes automatically offering the invitation when thesocial device is within a proximity threshold.
 12. The method of claim2, the social device resource comprising a first social device resourceand a second social device resource, wherein establishing access rightscomprises establishing distinct access rights for the first socialdevice resource and the second social device resource.
 13. The method ofclaim 2, wherein the access rights are established, at least in part,via a user interface associated with the social device resource. 14.Device circuitry for interacting with a social network infrastructure,the social network infrastructure hosting a social network circle, thedevice circuitry comprising: interface circuitry operable tocommunicatively couple with the social network infrastructure; andprocessing circuitry coupled to the interface circuitry, the processingcircuitry configured to: support interaction with the social networkinfrastructure via the interface circuitry, detect a social devicehaving a social device resource capable of being shared with members ofthe social network circle; offer an invitation to the social device toparticipate in the social network circle; receive an acceptance of theinvitation from the social device; automatically dock the social devicewith the social network circle to establish membership therein,membership of the social device within the social network circleseparate from membership of a corresponding user of the social device;establish access rights for the social device resource of the socialdevice; identify a request, from a second member of the social networkcircle, for access to the social device resource; and in response to therequest, permit interaction with the social device resource of thesocial device in accordance with the access rights.
 15. The devicecircuitry of claim 14, the processing circuitry further operable tosupport allocation of a social resource between multiple members of thesocial network circle, the allocation in accordance with the accessrights.
 16. The device circuitry of claim 15, allocation of a socialresource comprising arbitration of requests for access to the socialresource.
 17. The device circuitry of claim 14, the access rightscomprising at least a first level of access rights and a second level ofaccess rights.
 18. The device circuitry of claim 17, the first level ofaccess rights applicable to specified members of the social networkcircle, the second level of access rights applicable to non-members ofthe social network circle.
 19. A social network infrastructure used witha plurality of devices, the social network infrastructure comprising:processing circuitry configured to implement: a membership managementmodule that manages membership related to at least one social group, thesocial group including a plurality of devices, the membership managementmodule establishing memberships for the plurality of devices that areseparate from memberships of users of the plurality of devices; adocking module that manages docking of devices to the social group; anda resource allocation management module, wherein the membershipmanagement module, the docking module and the resource allocationmanagement module are operable to: detect a device having a socialdevice resource capable of being shared with members of the socialgroup; offer an invitation to the device to participate in the socialgroup; receive an acceptance of the invitation from the device;automatically dock the device with the social group to establishmembership therein; establish access rights for the social deviceresource of the device; identify a request, from a second member of thesocial group, for access to the social device resource; and in responseto the request, enable interaction with the social device resource inaccordance with the access rights.
 20. The social network infrastructureof claim 19, wherein detecting a device having a social device resourcecapable of being shared with members of the social group includesdetecting an attempt by the device to associate with an access point,and wherein offering an invitation to the device to participate in thesocial group includes automatically offering the invitation to thedevice upon detecting the attempt by the device to associate with theaccess point.
 21. The social network infrastructure of claim 19, whereindetecting a device having a social device resource capable of beingshared with members of the social group includes determining a locationof the device, and wherein offering an invitation to the social deviceto participate in the social group includes automatically offering theinvitation when the device is within a proximity threshold.